Verified with: 4.8.0-0.nightly-2021-03-22-104536
Adding an impact statement, following the template in [1]: Who is impacted? vSphere clusters with 100 or more nodes, which can have the vSphere problem detector stick with Degraded=True if it is interrupted. The detector is interrupted on updates, and can also be interrupted outside of updates (e.g. as a MachineConfig is rolled out, or a descheduler evicts pods, etc.) What is the impact? VSphereProblemDetectorControllerDegraded, which will stick any in-process OCP updates. No other in-cluster effects. How involved is remediation? oc edit storage cluster and set the operator Unmanaged. This has no downsides on vSphere, where all storage maintenance is in-tree, and the operator has nothing it manages directly. Is this a regression? Yes, the problem detector is new in 4.7, so the issue does not affect 4.6. All existing 4.7.z releases are vulnerable. [1]: https://github.com/openshift/enhancements/pull/475/files#diff-4be0a2148a92c5a0a6075d745727819df65063442b1d6ad5f39db27d7714287cR75-R91
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.8.2 bug fix and 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-2021:2438