Bug 1939555 - VSphereProblemDetectorControllerDegraded: context canceled during upgrade to 4.8.0
Summary: VSphereProblemDetectorControllerDegraded: context canceled during upgrade to ...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.8
Hardware: All
OS: All
Target Milestone: ---
: 4.8.0
Assignee: Hemant Kumar
QA Contact: Qin Ping
Depends On:
Blocks: 1936975
TreeView+ depends on / blocked
Reported: 2021-03-16 15:50 UTC by Hemant Kumar
Modified: 2021-07-27 22:54 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1936975
Last Closed: 2021-07-27 22:53:48 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift vsphere-problem-detector pull 34 0 None closed Bug 1939555: Fix deadlock when enqueing functions into the pool 2021-03-24 14:59:58 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:54:05 UTC

Comment 2 Qin Ping 2021-03-24 07:40:12 UTC
Verified with: 4.8.0-0.nightly-2021-03-22-104536

Comment 3 W. Trevor King 2021-03-24 15:43:09 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

Comment 7 errata-xmlrpc 2021-07-27 22:53:48 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.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.


Note You need to log in before you can comment on or make changes to this bug.