Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-27072

HCP does not deploy cloud provider kubevirt with configured node selectors

XMLWordPrintable

    • No
    • False
    • Hide

      None

      Show
      None

      This is a clone of issue OCPBUGS-25696. The following is the description of the original issue:
      —
      Description of problem:

          When deploying a HCP KubeVirt cluster using the hcp's --node-selector cli arg, that node selector is not applied to the "kubevirt-cloud-controller-manager" pods within the HCP namespace. 

This makes it not possible to pin the entire HCP pods to specific nodes.

      Version-Release number of selected component (if applicable):

          4.14

      How reproducible:

          100%

      Steps to Reproduce:

          1. deploy an hcp kubevirt cluster with the --node-selector cli option
    2.
    3.

      Actual results:

          the node selector is not applied to cloud provider kubevirt pod

      Expected results:

          the node selector should be applied to cloud provider kubevirt pod.

      Additional info:

            [OCPBUGS-27072] HCP does not deploy cloud provider kubevirt with configured node selectors

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Critical: OpenShift Container Platform 4.14.12 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-2024:0735

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Critical: OpenShift Container Platform 4.14.12 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-2024:0735

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Critical: OpenShift Container Platform 4.14.z 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-2024:0735

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Critical: OpenShift Container Platform 4.14.z 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-2024:0735

            Liangquan Li added a comment - 
            ➜  oc get node -l="OCPBUGS-25696=true"                                                                                                                                         
NAME                           STATUS   ROLES                         AGE    VERSION
ip-10-0-0-95.ec2.internal      Ready    control-plane,master,worker   101m   v1.27.10+28ed2d7
ip-10-0-101-233.ec2.internal   Ready    worker                        80m    v1.27.10+28ed2d7
ip-10-0-46-20.ec2.internal     Ready    worker                        78m    v1.27.10+28ed2d7
ip-10-0-85-204.ec2.internal    Ready    worker                        80m    v1.27.10+28ed2d7

➜  /usr/bin/hcp create cluster kubevirt --name d229fce33ca6e2402166 --node-pool-replicas 2 --memory 16Gi --cores 4 --root-volume-size 64 --pull-secret=/etc/ci-pull-credentials/.dockerconfigjson --release-image registry.build01.ci.openshift.org/ci-op-bli7mzky/release@sha256:51ac7113e894e81f5024c978e65c8607eee4dfc47444e1557689a47e45dc1ba8 --node-selector OCPBUGS-25696=true --etcd-storage-class=gp3-csi

➜  oc get pod -n clusters-d229fce33ca6e2402166 -o wide  | grep -v "ip-10-0-46-20.ec2.internal" | grep -v "ip-10-0-85-204.ec2.internal" | grep -v "ip-10-0-101-233.ec2.internal" | grep -v "ip-10-0-0-95.ec2.internal"
NAME                                                      READY   STATUS      RESTARTS   AGE   IP            NODE                           NOMINATED NODE   READINESS GATES
d229fce33ca6e2402166-721b4b7f-hshvr-console-logger        1/1     Running     0          53m   10.129.2.45   ip-10-0-9-108.ec2.internal     <none>           <none>
d229fce33ca6e2402166-721b4b7f-l5nwn-console-logger        1/1     Running     0          53m   10.129.2.47   ip-10-0-9-108.ec2.internal     <none>           <none>
virt-launcher-d229fce33ca6e2402166-721b4b7f-hshvr-pl5sl   0/1     Completed   0          51m   10.129.2.48   ip-10-0-9-108.ec2.internal     <none>           1/1

            looks good, we can move to verified

            Liangquan Li added a comment - ➜ oc get node -l= "OCPBUGS-25696= true " NAME STATUS ROLES AGE VERSION ip-10-0-0-95.ec2.internal Ready control-plane,master,worker 101m v1.27.10+28ed2d7 ip-10-0-101-233.ec2.internal Ready worker 80m v1.27.10+28ed2d7 ip-10-0-46-20.ec2.internal Ready worker 78m v1.27.10+28ed2d7 ip-10-0-85-204.ec2.internal Ready worker 80m v1.27.10+28ed2d7 ➜ /usr/bin/hcp create cluster kubevirt --name d229fce33ca6e2402166 --node-pool-replicas 2 --memory 16Gi --cores 4 --root-volume-size 64 --pull-secret=/etc/ci-pull-credentials/.dockerconfigjson --release-image registry.build01.ci.openshift.org/ci-op-bli7mzky/release@sha256:51ac7113e894e81f5024c978e65c8607eee4dfc47444e1557689a47e45dc1ba8 --node-selector OCPBUGS-25696= true --etcd-storage-class=gp3-csi ➜ oc get pod -n clusters-d229fce33ca6e2402166 -o wide | grep -v "ip-10-0-46-20.ec2.internal" | grep -v "ip-10-0-85-204.ec2.internal" | grep -v "ip-10-0-101-233.ec2.internal" | grep -v "ip-10-0-0-95.ec2.internal" NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES d229fce33ca6e2402166-721b4b7f-hshvr-console-logger 1/1 Running 0 53m 10.129.2.45 ip-10-0-9-108.ec2.internal <none> <none> d229fce33ca6e2402166-721b4b7f-l5nwn-console-logger 1/1 Running 0 53m 10.129.2.47 ip-10-0-9-108.ec2.internal <none> <none> virt-launcher-d229fce33ca6e2402166-721b4b7f-hshvr-pl5sl 0/1 Completed 0 51m 10.129.2.48 ip-10-0-9-108.ec2.internal <none> 1/1 looks good, we can move to verified

            OpenShift Jira Bot added a comment -

            Hi ocohen@redhat.com,

            Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            OpenShift Jira Bot added a comment - Hi ocohen@redhat.com , Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

              ocohen@redhat.com Oren Cohen
              openshift-crt-jira-prow OpenShift Prow Bot
              Liangquan Li Liangquan Li
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: