Upgrade of Red Hat AMQ Operator to v7.10 gives errors in the operator and broker logs

Solution Verified - Updated -

Issue

  • The upgrade of the AMQ Broker from 7.9.4 to 7.10.0 ends with errors in the Operator and the broker pods.
    Operator:

    amq-broker-operator 2022-06-21T09:40:05.089Z    ERROR    package k8s_actions    Failed to update *v1.Service    {"ActiveMQArtemis Name": "amq-wconsj-0-svc", "error": "Service \"amq-wconsj-0-svc\" is invalid: metadata.resourceVersion: Invalid value: \"\": must be specified for an update"}
    

    Broker:

    amq-container 2022-06-21 09:40:15,824 INFO  [org.openshift.ping.common.Utils] 3 attempt(s) with a 1000ms sleep to execute [GetServiceHosts] failed. Last failure was [java.net.UnknownHostException: amq-ping-svc]
    amq-container 2022-06-21 09:40:15,826 WARNING [org.jgroups.protocols.openshift.DNS_PING] No matching hosts found for service [amq-ping-svc]; continuing...
    

Environment

  • Red Hat AMQ Broker (AMQ) 7.x
  • Red Hat OpenShift Container (Openshift) 4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content