Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-5912

Restarting cluster-wide Operator pod causes all AMQ Brokers to be restarted in all namespaces

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • AMQ 7.9.2.OPR.1.GA
    • AMQ 7.9.1.OPR.1.GA
    • operator
    • None
    • False
    • False
    • User Experience
    • Hide
      1. Deploy AMQ Broker Operator cluster-wide
      2. Configure the Operator to watch all namespaces
      3. Create 2 or more namespaces
      4. Deploy an AMQ Broker on each namespace
      5. Delete or scale down & up the Operator pod in the openshift-operators namespace
      6. Watch the events in all AMQ Broker namespaces
      Show
      Deploy AMQ Broker Operator cluster-wide Configure the Operator to watch all namespaces Create 2 or more namespaces Deploy an AMQ Broker on each namespace Delete or scale down & up the Operator pod in the openshift-operators namespace Watch the events in all AMQ Broker namespaces

      After deploying some AMQ Brokers on different namespaces, all of them handled by a cluster-wide Operator watching all namespaces.  When you restart the Operator pod either by deleting the pod or scaling down and up the Deployment, it triggers the restart of all the AMQ Broker pods in all namespaces.

        1. amq-broker-operator.log.gz
          18 kB
          William Lovaton
        2. broker-events.log.gz
          0.8 kB
          William Lovaton

            gaohoward Howard Gao
            rhn-support-wlovaton William Lovaton
            Mikhail Krutov Mikhail Krutov
            Votes:
            1 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: