Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-26489

SNO Control Plane Fails to Come Up After Reboot On Cloud Deployments

XMLWordPrintable

    • Critical
    • No
    • 5
    • OCPEDGE Sprint 249
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      The MCO's gcp-e2e-op-single-node job https://prow.ci.openshift.org/job-history/gs/origin-ci-test/pr-logs/directory/pull-ci-openshift-machine-config-operator-master-e2e-gcp-op-single-node has been failing consistently since early Jan.
      
      It always fails on TestKernelArguments but that happens to be the first time where it gets the node to reboot, after which the node never comes up, so we don't get must-gather and (for some reason) don't get any console gathers either.
      
      This is only 4.16 and only single node. Doing the same test on HA gcp clusters yield no issues. The test itself doesn't seem to matter as the next test would fail the same way if it was skipped.
      
      This can be reproduced so far only via a 4.16 clusterbot cluster.

      Version-Release number of selected component (if applicable):

      4.16

      How reproducible:

      100%

      Steps to Reproduce:

          1. install SNO 4.16 cluster
          2. run MCO's TestKernelArguments
          3.
          

      Actual results:

      Node never comes back up

      Expected results:

      Test passes

      Additional info:

          

            ehila@redhat.com Egli Hila
            jerzhang@redhat.com Yu Qi Zhang
            Sergio Regidor de la Rosa Sergio Regidor de la Rosa
            Votes:
            0 Vote for this issue
            Watchers:
            17 Start watching this issue

              Created:
              Updated: