-
Bug
-
Resolution: Won't Do
-
Normal
-
None
-
None
-
None
job link
this is coming in the test case about "Check if alerts are firing during or after upgrade success" and the test log snippet is here:
{ 1 nodes violated upgrade expectations:
Node ip-10-0-150-237.ec2.internal went unready at 2022-05-04T09:35:33Z, never became ready again
}
There are a lot of "failures" in this job, but guessing they will all come back to why a node took a toss and
never came up ready during the reboot. The journal entries are empty so that's not much help.
The "oc get nodes" at the end of the job shows it NotReady.
ip-10-0-150-237.ec2.internal NotReady master 3h6m v1.23.5+70fb84c 10.0.150.237 <none> Red Hat Enterprise Linux CoreOS 410.84.202204261500-0 (Ootpa) 4.18.0-305.45.1.el8_4.x86_64 cri-o://1.23.2-8.rhaos4.10.git8ad5d25.el8
link to this job's testgrid for reference.
