Uploaded image for project: 'MicroShift'
  1. MicroShift
  2. USHIFT-1054

reboot test ignoring failures

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • openshift-4.13
    • None
    • None
    • None
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • uShift Sprint 234, uShift Sprint 235

      Description of problem (via pmatusza@redhat.com ):

       
      FYI Our e2e-reboot seems to be "broken"
      Example "successful" run
      e2e-reboot log:
      oc create -f -
      persistentvolumeclaim/test-claim created
      pod/test-pod created
      + set +ex
      waiting for pod condition
      error: timed out waiting for the condition on pods/test-pod
      pod posted ready status
      error happened, but +ex disabled catching itreboot-verify: some command failed, cluster-debug-info ran, but we're missing exit 1 here (same as e2e-greenboot recently)
       
      Version-Release number of selected component (if applicable):

      4.14, 4.13

      How reproducible: Every job?

      Steps to Reproduce: (see above)

      Actual results:

       

      Expected results:

       

      Additional info:

       

              jcope@redhat.com Jon Cope
              dhellman@redhat.com Doug Hellmann
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: