ActiveMQArtemisAddress are not created when ActiveMQArtemisSecurity applied before

Deploy CRs simultaneously: ActiveMQArtemis, ActiveMQArtemisAddress, ActiveMQArtemisSecurity and other Kubernetes resources.
After deployment, the operator starts the broker's pod, but it restarts in order to apply ActiveMQArtemisSecurity CR. Afterwards sometimes addresses and queues are created and sometimes not.
Furthermore, we observed that the pod is getting a new IP address after restart and the Jolokia call for configuring the addresses and queues fails and was using the old ip:

ERROR   controller_v2alpha3activemqartemisaddress   Creating ActiveMQArtemisAddress error for contractChangedNotificationMessageListener    {"error": "Post http://test:***@10.128.4.142:8161/console/jolokia/exec/org.apache.activemq.artemis:broker=%5C%22amq-broker%5C%22: dial tcp 10.129.3.243:8161: connect: connection refused"}