Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1901602

Summary:	Extra reboot during 4.5 -> 4.6 upgrade
Product:	OpenShift Container Platform	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	Machine Config Operator	Assignee:	Colin Walters <walters>
Status:	CLOSED ERRATA	QA Contact:	Michael Nguyen <mnguyen>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.6	CC:	jerzhang, mkrejci, sdodson, walters, wking
Target Milestone:	---	Keywords:	Upgrades
Target Release:	4.6.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-08 13:50:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1879099
Bug Blocks:

Comment 4 Michael Nguyen 2021-02-03 22:48:36 UTC

Verified on 4.6.0-0.nightly-2021-01-30-211400

$ oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.5.30    True        False         16m     Cluster version is 4.5.30
$ oc get nodes
NAME                                         STATUS   ROLES    AGE   VERSION
ip-10-0-145-139.us-west-2.compute.internal   Ready    worker   25m   v1.18.3+65bd32d
ip-10-0-158-82.us-west-2.compute.internal    Ready    master   35m   v1.18.3+65bd32d
ip-10-0-164-3.us-west-2.compute.internal     Ready    worker   25m   v1.18.3+65bd32d
ip-10-0-191-98.us-west-2.compute.internal    Ready    master   35m   v1.18.3+65bd32d
ip-10-0-218-56.us-west-2.compute.internal    Ready    master   35m   v1.18.3+65bd32d
ip-10-0-222-226.us-west-2.compute.internal   Ready    worker   25m   v1.18.3+65bd32d
$ oc debug node/ip-10-0-158-82.us-west-2.compute.internal -- chroot /host journalctl --list-boots
Starting pod/ip-10-0-158-82us-west-2computeinternal-debug ...
To use host binaries, run `chroot /host`
-1 6c9df0fe5d1b4eb59c07d2eb97239867 Wed 2021-02-03 20:36:09 UTC—Wed 2021-02-03 20:46:36 UTC
 0 b4cc14dda20b4da48919e42000a61e77 Wed 2021-02-03 20:46:52 UTC—Wed 2021-02-03 21:29:04 UTC

Removing debug pod ...
$ oc debug node/ip-10-0-164-3.us-west-2.compute.internal -- chroot /host journalctl --list-boots
Starting pod/ip-10-0-164-3us-west-2computeinternal-debug ...
To use host binaries, run `chroot /host`
-1 e8a0fa73cd534911ba494f2eea6057f5 Wed 2021-02-03 20:55:03 UTC—Wed 2021-02-03 20:56:46 UTC
 0 a1742d20e1024d09a4960775166cdafc Wed 2021-02-03 20:57:02 UTC—Wed 2021-02-03 21:29:30 UTC

Removing debug pod ...
$ oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.5.30    True        False         22m     Cluster version is 4.5.30
$ oc adm upgrade --to-image=registry.ci.openshift.org/ocp/release:4.6.0-0.nightly-2021-01-30-211400 --force
Updating to release image registry.ci.openshift.org/ocp/release:4.6.0-0.nightly-2021-01-30-211400
$ watch oc get clusterversion
$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.6.0-0.nightly-2021-01-30-211400   True        False         4m24s   Cluster version is 4.6.0-0.nightly-2021-01-30-211400
$ oc debug node/ip-10-0-158-82.us-west-2.compute.internal -- chroot /host journalctl --list-boots
Starting pod/ip-10-0-158-82us-west-2computeinternal-debug ...
To use host binaries, run `chroot /host`
-3 6c9df0fe5d1b4eb59c07d2eb97239867 Wed 2021-02-03 20:36:09 UTC—Wed 2021-02-03 20:46:36 UTC
-2 b4cc14dda20b4da48919e42000a61e77 Wed 2021-02-03 20:46:52 UTC—Wed 2021-02-03 22:18:13 UTC
-1 0d89b2a87038499d828bf45a56b24019 Wed 2021-02-03 22:18:31 UTC—Wed 2021-02-03 22:29:28 UTC
 0 83b419710e584beaa68f2e150654d3c7 Wed 2021-02-03 22:29:46 UTC—Wed 2021-02-03 22:46:56 UTC

Removing debug pod ...
$ oc debug node/ip-10-0-164-3.us-west-2.compute.internal -- chroot /host journalctl --list-boots
Starting pod/ip-10-0-164-3us-west-2computeinternal-debug ...
To use host binaries, run `chroot /host`
-2 e8a0fa73cd534911ba494f2eea6057f5 Wed 2021-02-03 20:55:03 UTC—Wed 2021-02-03 20:56:46 UTC
-1 a1742d20e1024d09a4960775166cdafc Wed 2021-02-03 20:57:02 UTC—Wed 2021-02-03 22:28:32 UTC
 0 87e354fb0ef74ea3a588d69483c4caa1 Wed 2021-02-03 22:28:48 UTC—Wed 2021-02-03 22:47:08 UTC

Comment 6 errata-xmlrpc 2021-02-08 13:50:51 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.6.16 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:0308