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

[Operator Image] Broker Operator doesn't pick up CR name after restart / update

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • AMQ 7.5.0.GA, AMQ 7.6.0.GA
    • operator
    • None
    • Hide
      Previously, if you created a clustered broker deployment of two or more brokers that were configured to use persistence and message migration, the Operator might generate an invalid name when instantiating the scaledown controller for message migration. Specifically, this issue occurred if the Operator had been restarted or its image had been updated prior to scaledown of the broker deployment. The result of this situation was that you needed to delete and recreate your broker deployment. This issue is now resolved.
      Show
      Previously, if you created a clustered broker deployment of two or more brokers that were configured to use persistence and message migration, the Operator might generate an invalid name when instantiating the scaledown controller for message migration. Specifically, this issue occurred if the Operator had been restarted or its image had been updated prior to scaledown of the broker deployment. The result of this situation was that you needed to delete and recreate your broker deployment. This issue is now resolved.
    • Documented as Resolved Issue
    • Hide

      New broker deployment must be created. Delete custom resource instance to delete stateful set and create it again to redeploy broker.

      Show
      New broker deployment must be created. Delete custom resource instance to delete stateful set and create it again to redeploy broker.
    • Hide
      1. Install AMQ broker operator
      2. Use custom resource to deploy AMQ broker with persistence and message migration enabled and at least 2 replicas
      3. Scale down and back up (restart) the operator or update (change) it's image
      4. Scale down broker
      5. Scaledown controller should not be able to start
      6. Look into logs of oerator
      Show
      Install AMQ broker operator Use custom resource to deploy AMQ broker with persistence and message migration enabled and at least 2 replicas Scale down and back up (restart) the operator or update (change) it's image Scale down broker Scaledown controller should not be able to start Look into logs of oerator

    Description

      If Custom Resource has name "my-broker" scale down controller is being created with label containing this name. unfortunately the name of custom resource won't apply in scaledown controller if operator has been restarted or updated while broker deployment with message migration enabled is running. Instead of "my-broker-amq-drainer" label "-amq-drainer" is used which violates naming rules (there is not alphanumeric character at the beginning but '-') and scaledown controller cannot be created.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2866 Sometimes when drainer starts it gets short hostname rather than full and can't join cluster

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-3021 Drainer pod is not started when broker is scaled down using AMQ operator

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              rhn-support-rkieley Roderick Kieley
              rvais Roman Vais
              Mikhail Krutov Mikhail Krutov
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: