Bug 1979431 - Manila CSI driver operator does not start due to setting "defaultNodeSelector" when upgrading OCP from 4.6.9 to 4.6.12
Summary: Manila CSI driver operator does not start due to setting "defaultNodeSelector...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-scheduler
Version: 4.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.6.z
Assignee: Jan Chaloupka
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-06 02:34 UTC by Hideshi Fukumoto
Modified: 2022-11-16 12:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-25 13:49:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift openshift-docs pull 34928 0 None open BZ-1979431: Clarifying behavior of the default node selector 2021-07-28 21:16:05 UTC
Github openshift openshift-docs pull 35894 0 None None None 2021-08-30 15:46:39 UTC
Red Hat Product Errata RHBA-2021:3197 0 None None None 2021-08-25 13:49:35 UTC

Comment 6 Jan Chaloupka 2021-07-29 15:12:27 UTC 
https://github.com/openshift/openshift-docs/pull/34992 merged
Comment 12 RamaKasturi 2021-08-11 09:02:29 UTC 
Moving the bug to verified state as the doc contains the detail explanation about how cluster wide default node selector & a node selector work together, what happens if both of them have the same key.
Comment 18 errata-xmlrpc 2021-08-25 13:49:22 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.6.43 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-2021:3197
Comment 20 RamaKasturi 2022-11-16 12:41:11 UTC 
Setting qe_test_coverage flag to '-' as the behaviour seen here is expected and not a bug. Documentation has been added with additional information on project node selector due to which the bug was raised at first.
Note You need to log in before you can comment on or make changes to this bug.