Bug 2034901 - post upgrade taints for UpdateInProgress were not removed from some of the nodes
Summary: post upgrade taints for UpdateInProgress were not removed from some of the nodes
Keywords:
Status: CLOSED DUPLICATE of bug 2035005
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Installation
Version: 4.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Simone Tiraboschi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-22 12:49 UTC by Debarati Basu-Nag
Modified: 2021-12-22 17:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-22 14:47:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 1 Simone Tiraboschi 2021-12-22 14:47:03 UTC
it's a pretty recent change in MCO:
https://github.com/openshift/machine-config-operator/pull/2686

please reopen a bug there if not removed at the end of OCP upgrade.

Comment 2 Debarati Basu-Nag 2021-12-22 15:58:26 UTC
@stirabos@redhat.com, currently the cluster is not undergoing any ocp upgrade and the nodes are still tainted:
=================================
[cnv-qe-jenkins@c01-cnv410-upg-6cltm-executor ~]$ kubectl get clusterversion -A
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.10.0-0.nightly-2021-12-21-130047   True        False         11h     Cluster version is 4.10.0-0.nightly-2021-12-21-130047
[cnv-qe-jenkins@c01-cnv410-upg-6cltm-executor ~]$ kubectl get node c01-cnv410-upg-6cltm-master-0 -o json | jq ".spec"
{
  "providerID": "openstack:///a098fde7-6bb8-4e78-a778-0579f81c3cec",
  "taints": [
    {
      "effect": "NoSchedule",
      "key": "node-role.kubernetes.io/master"
    },
    {
      "effect": "PreferNoSchedule",
      "key": "UpdateInProgress"
    }
  ]
}
[cnv-qe-jenkins@c01-cnv410-upg-6cltm-executor ~]$

Comment 3 Simone Tiraboschi 2021-12-22 17:29:50 UTC

*** This bug has been marked as a duplicate of bug 2035005 ***


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