Bug 2047779 - do not degrade cluster if storagepolicy creation fails
Summary: do not degrade cluster if storagepolicy creation fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.10
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.10.0
Assignee: Hemant Kumar
QA Contact: Penghao Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-28 14:16 UTC by Hemant Kumar
Modified: 2022-03-10 16:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:42:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift vmware-vsphere-csi-driver-operator pull 72 0 None Merged Bug 2047779: Never degrade cluster on storage policy syncResult 2022-01-31 23:03:00 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:43:04 UTC

Comment 1 Jan Safranek 2022-01-28 14:30:16 UTC 
This breaks upgrade from 4.9 to 4.10 when 4.10-ish OCP does not have permissions to create StoragePolicy in vCenter.

Actual results:
Storage is degraded, upgrade is stuck.

Expected results:
Cluster is upgraded, however, it's Upgradeable: false. Users have the whole 4.10 lifeycycle to fix OCP permissions in vCenter.
Comment 2 Jan Safranek 2022-01-28 14:34:40 UTC 
Correction, we don't set "Upgradeable: false", we keep it "true".
Comment 8 errata-xmlrpc 2022-03-10 16:42:52 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 (Moderate: OpenShift Container Platform 4.10.3 security 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-2022:0056
Note You need to log in before you can comment on or make changes to this bug.