Bug 1990852 - OpenShift nodes were upgraded after 15 days of cluster upgraded
Summary: OpenShift nodes were upgraded after 15 days of cluster upgraded
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Yu Qi Zhang
QA Contact: Rio Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-06 12:44 UTC by aygarg
Modified: 2021-11-08 17:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-08 17:40:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description aygarg 2021-08-06 12:44:30 UTC 
Description of problem:
The worker nodes and one of the master nodes were upgraded after 15 days of the last cluster upgrade instead of the same day. Due to some reason, the node upgrade was pending and then automatically triggered. It looks like the last upgrade was incomplete or partial because the os update is done only on few nodes which were not updated previously


Version-Release number of selected component (if applicable):
OpenShift 4.6.36
The cluster was upgraded from 4.6.32 to 4.6.36 on 2021-07-18.


Actual results:
There are 3 masters, 3 infra, 12 workers nodes in the cluster, out of which all worker nodes and 1 master node were upgraded on 1st and 2nd August instead of the same day of cluster upgrade.

Expected results:
The nodes should have been upgraded on 2021-07-18.

Additional info:
The cluster is running over AWS GovCloud as a BareMeatal installation (Disconnected). I will be sharing the cluster must-gather.
Note You need to log in before you can comment on or make changes to this bug.