Bug 1939555
| Summary: | VSphereProblemDetectorControllerDegraded: context canceled during upgrade to 4.8.0 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Hemant Kumar <hekumar> |
| Component: | Storage | Assignee: | Hemant Kumar <hekumar> |
| Storage sub component: | Operators | QA Contact: | Qin Ping <piqin> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | aos-bugs, chuffman, dahernan, hekumar, jsafrane, lmohanty, piqin, wking |
| Version: | 4.8 | Keywords: | Upgrades |
| Target Milestone: | --- | ||
| Target Release: | 4.8.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1936975 | Environment: | |
| Last Closed: | 2021-07-27 22:53:48 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: | |||
| Bug Blocks: | 1936975 | ||
|
Comment 2
Qin Ping
2021-03-24 07:40:12 UTC
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 |