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

No operator support for, upon startup, using the existing CR instances as a baseline to move forward from.

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Done
    • 7.6.0.CR3
    • None
    • operator
    • None
    • Hide
      Previously, when the AMQ Broker Operator started, it did not check for existing Custom Resource (CR) instances in your project. This issue meant that if you needed to restart the Operator (for example, to apply a new Operator image version), the Operator and the broker deployment were no longer in sync. In this situation you needed to delete and then recreate your broker deployment. This issue is now resolved.
      Show
      Previously, when the AMQ Broker Operator started, it did not check for existing Custom Resource (CR) instances in your project. This issue meant that if you needed to restart the Operator (for example, to apply a new Operator image version), the Operator and the broker deployment were no longer in sync. In this situation you needed to delete and then recreate your broker deployment. This issue is now resolved.
    • Documented as Resolved Issue
    • ?
    • Verified in a release

    Description

      As identified during discussion in ENTMQBR-3514 - 'Address not created if address CR is submitted before broker instantiated', a more general problem exists. The more general problem is that the operator doesn't go looking for existing CRs upon startup to ensure it is aware of existing instance that may already be running that it will need to manage and update.

      This should be addressed as it is particularly important for existing production deployments where a fix to the operator for a bug or CVE may require a slight bump to the operator container image, thus forcing an operator restart. At this point the operator would no longer be in sync with the existing deployment, but rather the deployment would need to be redeployed.

      In theory a broker cluster redeployment should result in the exact same deployment with minimal downtime, however steady state would be lost and unnecessary risk introduced.

      Attachments

        Activity

          People

            gaohoward Howard Gao
            rhn-support-rkieley Roderick Kieley
            Tiago Bueno Tiago Bueno
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: