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

SS can not recover itself after reaching a failure state

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • AMQ 7.10.0.OPR.3.GA
    • operator
    • None
    • False
    • None
    • False
    • Hide
      1. Create a correct non-crashing CR with 2 broker instances
      2. Wait for them to spawn
      3. Modify CR to include something which would crash brokers (in this instance, that would be jolokiaEnabled variable as this is currently bugged; however anything like a non-valid init container URL would also work)
      4. Wait for updates

      What actually happens is, at this point 1 broker of the 2 starts restarting, reaching a "crashloop" state according to Openshift status.

      This crashloop can not be reconciled from, reverting the change to Broker CR does nothing as Operator doesn't try to update the statefulset from this state.

       

      Only way to recover from this situation is SS removal for operator to re-create.

      Show
      Create a correct non-crashing CR with 2 broker instances Wait for them to spawn Modify CR to include something which would crash brokers (in this instance, that would be jolokiaEnabled variable as this is currently bugged; however anything like a non-valid init container URL would also work) Wait for updates What actually happens is, at this point 1 broker of the 2 starts restarting, reaching a "crashloop" state according to Openshift status. This crashloop can not be reconciled from, reverting the change to Broker CR does nothing as Operator doesn't try to update the statefulset from this state.   Only way to recover from this situation is SS removal for operator to re-create.

          gtully@redhat.com Gary Tully
          mkrutov Mikhail Krutov
          Votes:
          0 Vote for this issue
          Watchers:
          2 Start watching this issue

            Created:
            Updated:
            Resolved: