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

[sig-node] nodes should not go unready after being upgraded and go unready only once Failues

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • No
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      TRT is observing 10 out of 10 jobs showing failures for '[sig-node] nodes should not go unready after being upgraded and go unready only once Failues' The tuning operator is also showing as degraded around the time a single worker node is restarted multiple times in the latest nightly 4.14.0-0.nightly-2023-08-22-042716 aggregation run for gcp-ovn-rt-upgrade.

      https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.14-upgrade-from-stable-4.13-e2e-gcp-ovn-rt-upgrade/1693843197710569472

      The prior payload 4.14.0-0.nightly-2023-08-21-210813 did not exhibit the problem. The payload following 4.14.0-0.nightly-2023-08-22-042716 4.14.0-0.nightly-2023-08-22-121430 continues to show the node-tuning operator in a degraded state as well as a single worker node being restarted multiple times.

      The diff between the first bad payload and the last good https://amd64.ocp.releases.ci.openshift.org/releasestream/4.14.0-0.nightly/release/4.14.0-0.nightly-2023-08-22-042716?from=4.14.0-0.nightly-2023-08-21-210813 shows a limited set of changes

              jmencak Jiri Mencak
              rh-ee-fbabcock Forrest Babcock
              None
              None
              Liquan Cui Liquan Cui
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: