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

7.10-opr-3 does not fix the PVC ownerRef for 7.10-opr-2 users

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • AMQ 7.10.1.OPR.1.GA
    • AMQ 7.10.0.OPR.3.GA
    • operator
    • False
    • None
    • False
    • Hide
      If you upgrade to 7.10.0-opr-2 and scale up your deployment, the new PVCs are created with an `ownerReference` attribute that can cause data loss if you later delete the deployment CR.
      For example, if you deploy 7.10.0-opr-1, upgrade to 7.10.0-opr-2 and then scale from 3 to 4 broker instances, you could lose data if you delete the `ActiveMQArtemis` CR only if the mapped PV is ephemeral

      To workaround this issue, you can:
      * Skip the 7.10.0-opr-2 upgrade if possible.
      * Avoid scaling up your deployment while the 7.10.0-opr-2 release is active in your cluster. You can scale up after you deploy 7.10.0-opr-3.
      * Avoid deleting the deployment CR until a later release resolves this issue.
      * Manually remove the `ownerReference` value for the PVCs created by the stateful set template.
      Show
      If you upgrade to 7.10.0-opr-2 and scale up your deployment, the new PVCs are created with an `ownerReference` attribute that can cause data loss if you later delete the deployment CR. For example, if you deploy 7.10.0-opr-1, upgrade to 7.10.0-opr-2 and then scale from 3 to 4 broker instances, you could lose data if you delete the `ActiveMQArtemis` CR only if the mapped PV is ephemeral To workaround this issue, you can: * Skip the 7.10.0-opr-2 upgrade if possible. * Avoid scaling up your deployment while the 7.10.0-opr-2 release is active in your cluster. You can scale up after you deploy 7.10.0-opr-3. * Avoid deleting the deployment CR until a later release resolves this issue. * Manually remove the `ownerReference` value for the PVCs created by the stateful set template.

    Description

      The 7.10-opr-3 release removes the PVC's ownerReference in order to avoid the risk of data loss when deleting an ActiveMQArtemuis CR.

      This works, but the upgrade to 7.10-opr-3 does not fix the issue for customers who previously upgraded to 7.10-opr-2. This means that they are still at risk of losing data if an ActiveMQArtemis CR is deleted. To avoid that risk, they would have to manually delete the ownerReference from each PVC (this could be a release note).

      No KCS can help with this, because it would be too late. The proper solution would be that the operator automatically removes any PVC ownerReference.

      Attachments

        Issue Links

          account is impacted by

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-6886 [Operator] Deleting ActiveMQArtemis also deletes the PVC

          • 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
          is related to

          Task - Represents a small unit of work that is not end-user facing. ENTMQBR-6884 Mention 'retain' policy required for persistence

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

          Page Loading...

          Activity

            People

              gaohoward Howard Gao
              rhn-support-fvaleri Federico Valeri
              Roman Vais Roman Vais
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: