#OCPBUGS-27059 | issue | [origin] Monitors must not flake for a set of pods life-cycles from Running to Pending CLOSED | |
Issue 15715077: [origin] Monitors must not flake for a set of pods life-cycles from Running to Pending Description: Description of problem: Version-Release number of selected component (if applicable): {code:none} 4.16{code} How reproducible: {code:none} During upgrade, it happens frequently{code} Steps to Reproduce: {code:none} 1. Launch upgrade 2. Observer monitor test results specicially looking at test outcome of "[sig-node] pods should never transition back to pending" {code} Actual results: {code:none} Flakes for a number of pods that should have an exception{code} Expected results: {code:none} Ignores set of pods that should be allowed to go from Running to Pending {code} Additional info: {code:none} There was a bug that described this problem: https://bugzilla.redhat.com/show_bug.cgi?id=1933760 Outcome was https://github.com/kubernetes/kubernetes/issues/106390 Test should not flake for pods that meet the criteria defined in the above issue. I created this issue because of: https://redhat-internal.slack.com/archives/CE4L0F143/p1704459757540179 David eads: " TODO here is to have the monitor allow the transition for daemonset pods with init containers shortly after a node restart."{code} Status: CLOSED | |||
periodic-ci-openshift-release-master-ci-4.8-upgrade-from-stable-4.7-e2e-gcp-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
#1784416954916802560 | junit | 43 hours ago | |
# [sig-node] pods should never transition back to pending Marked as flake until https://bugzilla.redhat.com/show_bug.cgi?id=1933760 is fixed |
Found in 100.00% of runs (100.00% of failures) across 1 total runs and 1 jobs (100.00% failed) in 89ms - clear search | chart view - source code located on github