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

[Operator, upgrade] 7.10 versions of operator tend to remove stateful set during upgrade

    XMLWordPrintable

Details

    • False
    • None
    • False
    • Documentation (Ref Guide, User Guide, etc.), Release Notes, User Experience
    • Hide

      Version within the channel:

      1. Install operator 7.10.0-opr3 (OLM and 7.10.x channel used)
      2. Deploy CR with basic broker deployment with persistence and message migration size (size doesn't matter this one has just been used during testing) and upgrades enabled
      3. Update index image to trigger the upgrade procedure
      4. Operator 7.10.1-opr1 will be installed and takes over the deployment
      5. expectation: Broker pod with highest ordinal number will shut down and spins back up. Then the same happens to the pod with lower ordinal number till all pods have been updated.
      6. result: all pods will terminate and start spinning up like in case of new deployment.
      Show
      Version within the channel: Install operator 7.10.0-opr3 (OLM and 7.10.x channel used) Deploy CR with basic broker deployment with persistence and message migration size (size doesn't matter this one has just been used during testing) and upgrades enabled Update index image to trigger the upgrade procedure Operator 7.10.1-opr1 will be installed and takes over the deployment expectation: Broker pod with highest ordinal number will shut down and spins back up. Then the same happens to the pod with lower ordinal number till all pods have been updated. result: all pods will terminate and start spinning up like in case of new deployment.

    Description

      In case of upgrading the operator version, usually there are no changes of the custom resources or anything else that would require update of immutable field in stateful set. Only the container image url is changed when upgrades of the broker deployment are enabled. That change should result only in rolling update, where individual pods are terminated and then brought back up one by one. That's the behavior observed with upgrades of 7.8 and 7.9 aligned operators. With the 7.10 versions, upgrades of the stateful set seem to be failing and therefore operator will remove and recreate it. That causes all pods to shut down at the same time and causes short outage in service availability. This should not be happening.

      Attachments

        Issue Links

          duplicates

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-6855 [Operator] Pod's custom labels cannot be updated

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-5240 Implement Metering Labels in Broker OCP Images

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-7396 [Operator, upgrade] the upgrade to 7.10.1 fails to create new Acceptor/Connector *v1.Service

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-7105 The update of spec.version in ActiveMQArtemis CR doesn't trigger the rolling update strategy

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-7878 [LTS] The update of spec.version in ActiveMQArtemis CR doesn't trigger the rolling update strategy

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          mentioned in

          Page Loading...

          Activity

            People

              gtully@redhat.com Gary Tully
              rvais Roman Vais
              Roman Vais Roman Vais
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: