Bug 2083370 - CVO exits upgrade immediately rather than waiting for etcd backup
Summary: CVO exits upgrade immediately rather than waiting for etcd backup
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 4.10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.10.z
Assignee: Jack Ottofaro
QA Contact: Yang Yang
URL:
Whiteboard:
: 2086287 (view as bug list)
Depends On: 2072389
Blocks: 2076793
TreeView+ depends on / blocked
 
Reported: 2022-05-09 19:32 UTC by Jack Ottofaro
Modified: 2022-05-23 13:25 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2072389
Environment:
Last Closed: 2022-05-23 13:25:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-version-operator pull 776 0 None Merged Bug 2083370: Do not save desired update on load failures 2022-06-01 05:39:33 UTC
Red Hat Product Errata RHBA-2022:2258 0 None None None 2022-05-23 13:25:34 UTC

Comment 1 Yang Yang 2022-05-10 07:20:05 UTC 
PR pre-merge verification:

1. Launch a cluster using cluster-bot
launch openshift/cluster-version-operator#776 gcp

# oc adm upgrade 
Cluster version is 4.10.0-0.ci.test-2022-05-10-061215-ci-ln-wkqqklb-latest

warning: Cannot display available updates:
  Reason: NoChannel
  Message: The update channel has not been configured.


2. Upgrade to 4.11

# oc adm upgrade --to-image=registry.ci.openshift.org/ocp/release@sha256:a655fcffc1bf299563471eb71625eedf142b4a953f15dc2c8fa76438092495ac --allow-explicit-upgrade 
warning: The requested upgrade image is not one of the available updates.You have used --allow-explicit-upgrade for the update to proceed anyway
Updating to release image registry.ci.openshift.org/ocp/release@sha256:a655fcffc1bf299563471eb71625eedf142b4a953f15dc2c8fa76438092495ac

3. Check cv conditions
# oc get -o json clusterversion version | jq -r '.status.conditions[] | .lastTransitionTime + " " + .type + "=" + .status + " " + .reason + ": " + .message'
2022-05-10T06:19:23Z RetrievedUpdates=False NoChannel: The update channel has not been configured.
2022-05-10T06:51:47Z ReleaseAccepted=False PreconditionChecks: Preconditions failed for payload loaded version="4.11.0-0.nightly-2022-05-07-161754" image="registry.ci.openshift.org/ocp/release@sha256:a655fcffc1bf299563471eb71625eedf142b4a953f15dc2c8fa76438092495ac": Precondition "EtcdRecentBackup" failed because of "UpgradeBackupInProgress": RecentBackup: Backup pod phase: "Pending"
2022-05-10T06:47:16Z Available=True : Done applying 4.10.0-0.ci.test-2022-05-10-061215-ci-ln-wkqqklb-latest
2022-05-10T06:47:16Z Failing=False : 
2022-05-10T06:47:16Z Progressing=False : Cluster version is 4.10.0-0.ci.test-2022-05-10-061215-ci-ln-wkqqklb-latest

# oc get -o json clusterversion version | jq -r '.status.conditions[] | .lastTransitionTime + " " + .type + "=" + .status + " " + .reason + ": " + .message'
2022-05-10T06:19:23Z RetrievedUpdates=False NoChannel: The update channel has not been configured.
2022-05-10T06:52:02Z ReleaseAccepted=True PayloadLoaded: Payload loaded version="4.11.0-0.nightly-2022-05-07-161754" image="registry.ci.openshift.org/ocp/release@sha256:a655fcffc1bf299563471eb71625eedf142b4a953f15dc2c8fa76438092495ac"
2022-05-10T06:47:16Z Available=True : Done applying 4.10.0-0.ci.test-2022-05-10-061215-ci-ln-wkqqklb-latest
2022-05-10T06:47:16Z Failing=False : 
2022-05-10T06:52:02Z Progressing=True : Working towards 4.11.0-0.nightly-2022-05-07-161754: 9 of 795 done (1% complete)

Look good to me.
Comment 5 W. Trevor King 2022-05-16 21:55:34 UTC 
*** Bug 2086287 has been marked as a duplicate of this bug. ***
Comment 7 errata-xmlrpc 2022-05-23 13:25:12 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 (OpenShift Container Platform 4.10.15 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/RHBA-2022:2258
Note You need to log in before you can comment on or make changes to this bug.