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

Broker pod still in a pending state after update CR from a invalid node label to a valid one

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • AMQ 7.10.0.GA
    • operator
    • None
    • False
    • None
    • False
    • Hide

      You can workaround this by deleting the CR and redeploy it with the correct node name.

      Show
      You can workaround this by deleting the CR and redeploy it with the correct node name.
    • Hide
      • Add a label to a node:
        oc label nodes brk410-r968d-worker-0-8qjkx node_selector_label=test-label
      • Add the node selector to broker CR:
        spec:
          deploymentPlan:
            nodeSelector:
              node_selector_label: "test-label"
      • Deploy the CR:
        oc apply -f ./node_selector_broker_activemqartemis_cr.yaml
      • The pod goes to running state
        oc get pods
        ex-aao-ss-0                                     1/1     Running   0          108s   10.131.0.26   brk410-r968d-worker-0-8qjkx   <none>           <none>
      • Change the CR to a invalid label:
        spec:
          deploymentPlan:
            nodeSelector:
              node_selector_label: "test-label-invalid"
      • Deploy the updated CR:
        oc apply -f ./node_selector_broker_activemqartemis_cr.yaml
      • The pod goes to pending state
        oc get pods
        ex-aao-ss-0                                     0/1     Pending       0          0s     <none>        <none>                        <none>           <none>
      • Change the CR back to a valid label:
        spec:
          deploymentPlan:
            nodeSelector:
              node_selector_label: "test-label"
      • The pod does not get back to running state:
        oc get pods
        ex-aao-ss-0                                     0/1     Pending       0          0s     <none>        <none>                        <none>           <none>
      Show
      Add a label to a node: oc label nodes brk410-r968d-worker-0-8qjkx node_selector_label=test-label Add the node selector to broker CR: spec:   deploymentPlan:     nodeSelector:       node_selector_label: "test-label" Deploy the CR: oc apply -f ./node_selector_broker_activemqartemis_cr.yaml The pod goes to running state oc get pods ex-aao-ss-0                                     1/1     Running   0          108s   10.131.0.26   brk410-r968d-worker-0-8qjkx   <none>           <none> Change the CR to a invalid label: spec:   deploymentPlan:     nodeSelector:       node_selector_label: "test-label-invalid" Deploy the updated CR: oc apply -f ./node_selector_broker_activemqartemis_cr.yaml The pod goes to pending state oc get pods ex-aao-ss-0                                     0/1     Pending       0          0s     <none>        <none>                        <none>           <none> Change the CR back to a valid label: spec:   deploymentPlan:     nodeSelector:       node_selector_label: "test-label" The pod does not get back to running state: oc get pods ex-aao-ss-0                                     0/1     Pending       0          0s     <none>        <none>                        <none>           <none>

      When I deploy the CR with a valid label on node_selector and after the pod is running, I changed the label to a invalid one (not existent on any node). So, the pod is terminated (as expected) and then move the a pending state as there is not elegible nodes to let it run (as expected). But if I change the CR again to a valid label and apply it, I expect it to be terminated and started again in the new label that I provided but it does not happen. The pod keeps in the pending state. So, to get it running again I need to delete the CR and create again.

       

      As stated by dev team, this issue may be fixed in https://github.com/artemiscloud/activemq-artemis-operator/pull/184

       

              rhn-support-rkieley Roderick Kieley
              tbueno@redhat.com Tiago Bueno
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: