emqx 5.3.2 with emqx-operator won't start on k8s about emqx HOT 5 CLOSED

@jiangwensm please help us to investigate this by providing test scenario to reproduce the issue as minimally and precisely as possible.

from emqx.

@jiangwensm please help us to investigate this by providing test scenario to reproduce the issue as minimally and precisely as possible.

@id edit File Acl Content through dashboard，and restart replicant Pod

from emqx.

the docs says:

If file-based authorizer is editted through Dashboard or REST API, EMQX stores the new file to data/authz/acl.conf and stops reading the configuration in the original file.

cluster.hocon(stores the acl file path)：

If a certain cluster node is restarted or some new nodes are added, the node will automatically copy and apply the configuration file cluster.hocon from other nodes within the cluster, therefore there is no need nor recommended to configure it manually.

according to the docs, I guess it copies edited cluster.hocon from other Pods, and won't copy data/authz/acl.conf, thus resulted in this problem.

from emqx.

Thanks, I managed to reproduce the issue. Verifying with the team.

from emqx.

@jiangwensm we have identified that this issue is with the emqx-operator.

I'm going to close this issue now since there is no bug in EMQX. Please feel free to follow emqx/emqx-operator#983 instead.

from emqx.