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

Infrequently, creating a CR instance with size n > 1 causes the the nth broker pod to start and immediately restart once

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Done
    • 7.5.0.CR1
    • None
    • operator
    • Release Notes
    • Hide
      Previously, if you used a Custom Resource (CR) instance to deploy a broker cluster via the {BrokerName} Operator, the final broker Pod in the deployment (as determined by the `size` attribute of your CR) started and then immediately restarted one time before it was usable. This issue is now resolved. None of the broker Pods in the deployment undergo a restart before they are usable.
      Show
      Previously, if you used a Custom Resource (CR) instance to deploy a broker cluster via the {BrokerName} Operator, the final broker Pod in the deployment (as determined by the `size` attribute of your CR) started and then immediately restarted one time before it was usable. This issue is now resolved. None of the broker Pods in the deployment undergo a restart before they are usable.
    • Documented as Resolved Issue

    Description

      When instantiating an ActiveMQArtemis custom resource instance if you want say 3 brokers and you set size to 3 when you are creating the instance when the 3rd broker pod starts, it will successfully start, then restart, then be usable.

      However if you first set size to 1, create and wait for it to be ready, then set size to 2 and wait for it to be ready, and then set size to 3 then neither the 1st, 2nd or 3rd broker pods have an extra restart. In both cases you are left with a normal broker cluster at the point when all three are running and marked ready in OpenShift.

      Could be timing in the local OCP environment leading to the readinessProbe timing out or could be a bug related to the scaling state.

      Attachments

        Activity

          People

            rhn-support-rkieley Roderick Kieley
            rhn-support-rkieley Roderick Kieley
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: