-
Bug
-
Resolution: Done
-
Major
-
AMQ 7.9.4.OPR.4.GA
-
None
-
False
-
None
-
False
-
Applying the following activemqartemisAddress CR:
apiVersion: broker.amq.io/v2alpha3 kind: ActiveMQArtemisAddress metadata: name: dla-uat namespace: amq spec: addressName: DLA applyToCrNames: - ex-aao1 queueConfiguration: durable: true maxConsumers: 50 purgeOnNoConsumers: false routingType: anycast
ends with the following errors in the operator and the address is not created:
2022-06-29T09:19:30.759Z INFO controller_v2alpha3activemqartemisaddress New Jolokia with {"Request.Namespace": "messagebroker", "Request.Name": "dla-uat", "User: ": "admin", "Protocol: ": "https"} 2022-06-29T09:19:30.759Z INFO controller_v2alpha3activemqartemisaddress Finally we gathered some mgmt arry {"size": 2} 2022-06-29T09:19:30.773Z DPANIC controller_v2alpha3activemqartemisaddress odd number of arguments passed as key-value pairs for logging {"ignored key": "DLA"} github.com/go-logr/zapr.handleFields
- is depended on by
-
ENTMQBR-6834 Operator: unable to created Addresses: AMQ229203: Address Does Not Exist: xxx and data "}
- Closed
- relates to
-
ENTMQBR-6878 [Operator] Address/Queue cannot be created if the "applyToCrNames" is used
- Closed