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

Pod Status pod names do not reflect the reality

    XMLWordPrintable

Details

    • Bug
    • Status: New
    • Major
    • Resolution: Unresolved
    • AMQ 7.7.0.GA
    • None
    • operator
    • None
    • Hide
      For an Operator-based broker deployment in a given OpenShift project, if you use the `oc get pod` command to list the broker Pods, the ordinal values for the Pods start at `0`, for example, `amq-operator-test-broker-ss-0`. However, if you use the `oc describe` command to get the status of broker Pods created from the `activemqartmises` Custom Resource (that is, `oc describe activemqartemises`), the Pod ordinal values incorrectly start at `1`, for example, `amq-operator-test-broker-ss-1`. There is no way to work around this issue.
      Show
      For an Operator-based broker deployment in a given OpenShift project, if you use the `oc get pod` command to list the broker Pods, the ordinal values for the Pods start at `0`, for example, `amq-operator-test-broker-ss-0`. However, if you use the `oc describe` command to get the status of broker Pods created from the `activemqartmises` Custom Resource (that is, `oc describe activemqartemises`), the Pod ordinal values incorrectly start at `1`, for example, `amq-operator-test-broker-ss-1`. There is no way to work around this issue.
    • Documented as Known Issue

    Description

      Pods listed in AMQ Broker status are indexed from 1, whereas the real operator pods are indexed from 0, thus the values (pod names) listed in Pod Status do not reflect the reality.

      amq-broker-operator.v0.15.0
      Deploy an AMQ Broker operator CR with size=2 and watch the activemqartemises resource.

      The pod names are indexed from 0

      $ oc get pod
      NAME                                   READY   STATUS              RESTARTS   AGE
      ...
      amq-operator-test-broker-ss-0          1/1     Running             0          40s
      amq-operator-test-broker-ss-1          0/1     ContainerCreating   0          3s
      

      but pods listed in Pod Status are indexed from 1

      $ oc describe activemqartemises
      ...
      Status:
        Pod Status:
          Ready:
            amq-operator-test-broker-ss-1
          Starting:
            amq-operator-test-broker-ss-2
      

      Attachments

        Issue Links

          Activity

            People

              rhn-support-rkieley Roderick Kieley
              pkremens@redhat.com Petr Kremensky (Inactive)
              Mikhail Krutov Mikhail Krutov
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: