Uploaded image for project: 'OpenShift SDN'
  1. OpenShift SDN
  2. SDN-2994

failure in test case "[sig-node] static pods should start after being created"

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Normal
    • None
    • None
    • None
    • SDN Sprint 218
    • 0
    • 0

    Description

      job link

      must-gather

      log snippet from e2e log:

      {  static pod lifecycle failure - static pod: "kube-controller-manager" in namespace: "openshift-kube-controller-manager" for revision: 6 on node: "ci-op-7902lhdb-5cb9e-fz8c5-master-2" didn't show up, waited: 2m30s}

      the normal output from the openshift-tests stdout doesn't have anything more than the above. hopefully there is other info in the
      other artifacts to figure out what is really wrong here.

      link to this job's testgrid for reference.

       

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. SDN-2988 failure in test case "[sig-network][Feature:EgressFirewall] when using openshift ovn-kubernetes should ensure egressfirewall is created"

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          links to

          GitHub openshift/origin#26880: Bug 2060498: only add failure when no event was found for the target revision

          Activity

            People

              rravaiol@redhat.com Riccardo Ravaioli
              jluhrsen Jamo Luhrsen
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: