Uploaded image for project: 'A-MQ Messaging-as-a-Service'
  1. A-MQ Messaging-as-a-Service
  2. ENTMQMAAS-2679

OCP 4.7 upgrade tests failing to install AMQ Online 1.6 (0/6 nodes are available: 3 Insufficient memory)

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 1.7.0
    • None
    • systemtests
    • None
    • False
    • False
    • Undefined

    Description

      We are seeing the upgrade tests failing on 4.7 on the install of AMQ Online 1.6 (i.e. before the upgrade to the new code has taken place). The brokers are failing to become ready due to a resource issue.

      java.lang.IllegalStateException: Failed to wait for: 5 match
      at io.enmasse.systemtest.isolated.upgrade.UpgradeTest.doTestUpgrade(UpgradeTest.java:256)
      at io.enmasse.systemtest.isolated.upgrade.UpgradeTest.testUpgradeAnsible(UpgradeTest.java:167)

      https://maas-jenkins-csb-amq-online.apps.ocp4.prod.psi.redhat.com/job/amq-online-downstream/job/1.7/job/amq-online-1.7-oc4.7-upgrade/

      amq-online-infra 10m Normal SuccessfulCreate statefulset/broker-365ea72-town create Pod broker-365ea72-town-0 in StatefulSet broker-365ea72-town successful
      amq-online-infra 10m Normal SuccessfulCreate statefulset/broker-365ea72-town create Claim data-broker-365ea72-town-0 Pod broker-365ea72-town-0 in StatefulSet broker-365ea72-town success
      amq-online-infra 10m Warning FailedScheduling pod/broker-365ea72-town-0 0/6 nodes are available: 3 Insufficient memory, 3 node(s) had taint

      {node-role.kubernetes.io/master: }

      , that the pod didn't tolerate.
      amq-online-infra 10m Normal WaitForFirstConsumer persistentvolumeclaim/data-broker-365ea72-town-0 waiting for first consumer to be created before binding
      amq-online-infra 10m Warning FailedScheduling pod/broker-365ea72-town-0 0/6 nodes are available: 3 Insufficient memory, 3 node(s) had taint

      {node-role.kubernetes.io/master: }

      , that the pod didn't tolerate.
      amq-online-infra 10m Normal SuccessfulCreate statefulset/broker-365ea72-4nei create Pod broker-365ea72-4nei-0 in StatefulSet broker-365ea72-4nei successful
      amq-online-infra 10m Warning FailedScheduling pod/broker-365ea72-bw8f-0 0/6 nodes are available: 3 Insufficient memory, 3 node(s) had taint

      {node-role.kubernetes.io/master: }

      , that the pod didn't tolerate.
      amq-online-infra 10m Normal SuccessfulCreate statefulset/broker-365ea72-bw8f create Claim data-broker-365ea72-bw8f-0 Pod broker-365ea72-bw8f-0 in StatefulSet broker-365ea72-bw8f success
      amq-online-infra 10m Normal SuccessfulCreate statefulset/broker-365ea72-bw8f create Pod broker-365ea72-bw8f-0 in StatefulSet broker-365ea72-bw8f successful
      amq-online-infra 10m Warning FailedScheduling pod/broker-365ea72-bw8f-0 0/6 nodes are available: 3 Insufficient memory, 3 node(s) had taint

      {node-role.kubernetes.io/master: }

      , that the pod didn't tolerate.
      amq-online-infra 10m Normal SuccessfulCreate statefulset/broker-365ea72-4nei create Claim data-broker-365ea72-4nei-0 Pod broker-365ea72-4nei-0 in StatefulSet broker-365ea72-4nei success
      amq-online-infra 9m43s Warning FailedScheduling pod/broker-365ea72-4nei-0 0/6 nodes are available: 3 Insufficient memory, 3 node(s) had taint

      {node-role.kubernetes.io/master: }

      , that the pod didn't tolerate.
      amq-online-infra 10m Warning FailedScheduling pod/broker-365ea72-4nei-0 0/6 nodes are available: 3 Insufficient memory, 3 node(s) had taint

      {node-role.kubernetes.io/master: }

      , that the pod didn't tolerate.
      a

      Attachments

        Activity

          People

            dkornel@redhat.com David Kornel
            keithbwall Keith Wall
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: