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

CSI topology can be disabled even though the env is compatible

    • ?
    • Important
    • No
    • ShiftStack Sprint 250, ShiftStack Sprint 251, ShiftStack Sprint 252
    • 3
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      Description of problem: In an environment with the following zones, topology was disabled while it should be enabled by default

      $ openstack availability zone list --compute
      +-----------+-------------+
      | Zone Name | Zone Status |
      +-----------+-------------+
      | AZ-0      | available   |
      | AZ-1      | available   |
      | AZ-2      | available   |
      +-----------+-------------+
      
      $ openstack availability zone list --volume
      +-----------+-------------+
      | Zone Name | Zone Status |
      +-----------+-------------+
      | nova      | available   |
      | AZ-0      | available   |
      | AZ-1      | available   |
      | AZ-2      | available   |
      +-----------+-------------+
          

      We have a check that verify the number of zones is identical for compute and volumes. This check should be removed. We want however to ensure that for every compute zone we have a matching volume zone.

            [OCPBUGS-30951] CSI topology can be disabled even though the env is compatible

            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.16.0 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:0041

            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.16.0 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:0041

            Ramón Lobillo added a comment - - edited

            Verified on 4.16.0-0.nightly-2024-04-23-032717 on top of RHOS-17.1-RHEL-9-20240123.n.1

            [stack@undercloud-0 ~]$ oc get -n openshift-cluster-csi-drivers cm/cloud-conf -o yaml
            apiVersion: v1
            data:
              cloud.conf: |
                [Global]
                region      = regionOne
                ca-file     = /etc/kubernetes/static-pod-resources/configmaps/cloud-config/ca-bundle.pem
                use-clouds  = true
                clouds-file = /etc/kubernetes/secret/clouds.yaml
                cloud       = openstack    [LoadBalancer]
                floating-network-id = 360f546c-ffbc-47bf-9adb-6585d09449cc
              enable_topology: "true"
            kind: ConfigMap
            metadata:
              creationTimestamp: "2024-04-26T16:28:41Z"
              name: cloud-conf
              namespace: openshift-cluster-csi-drivers
              resourceVersion: "10371"
              uid: e7734ceb-248d-4716-8c33-20bf3cecdd26
             

            where:

            (shiftstack) [stack@undercloud-0 ~]$ openstack availability zone list --compute
            +-----------+-------------+
            | Zone Name | Zone Status |
            +-----------+-------------+
            | AZ-0      | available   |
            | AZ-1      | available   |
            | AZ-2      | available   |
            +-----------+-------------+
            (shiftstack) [stack@undercloud-0 ~]$ openstack availability zone list --volume
            +-----------+-------------+
            | Zone Name | Zone Status |
            +-----------+-------------+
            | nova      | available   |
            | AZ-0      | available   |
            | AZ-1      | available   |
            | AZ-2      | available   |
            +-----------+-------------+
              

             

            Furthermore, pods with cinder PVCs are created in the matching nova/cinder AZs.

            Ramón Lobillo added a comment - - edited Verified on 4.16.0-0.nightly-2024-04-23-032717 on top of RHOS-17.1-RHEL-9-20240123.n.1 [stack@undercloud-0 ~]$ oc get -n openshift-cluster-csi-drivers cm/cloud-conf -o yaml apiVersion: v1 data:   cloud.conf: |     [Global]     region      = regionOne     ca-file     = /etc/kubernetes/ static -pod-resources/configmaps/cloud-config/ca-bundle.pem     use-clouds  = true     clouds-file = /etc/kubernetes/secret/clouds.yaml     cloud       = openstack    [LoadBalancer]     floating-network-id = 360f546c-ffbc-47bf-9adb-6585d09449cc   enable_topology: " true " kind: ConfigMap metadata:   creationTimestamp: "2024-04-26T16:28:41Z"   name: cloud-conf   namespace: openshift-cluster-csi-drivers   resourceVersion: "10371"   uid: e7734ceb-248d-4716-8c33-20bf3cecdd26 where: (shiftstack) [stack@undercloud-0 ~]$ openstack availability zone list --compute +-----------+-------------+ | Zone Name | Zone Status | +-----------+-------------+ | AZ-0      | available   | | AZ-1      | available   | | AZ-2      | available   | +-----------+-------------+ (shiftstack) [stack@undercloud-0 ~]$ openstack availability zone list --volume +-----------+-------------+ | Zone Name | Zone Status | +-----------+-------------+ | nova      | available   | | AZ-0      | available   | | AZ-1      | available   | | AZ-2      | available   | +-----------+-------------+     Furthermore, pods with cinder PVCs are created in the matching nova/cinder AZs.

            Hi maandre@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 maandre@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.

            Removing the Triaged label because:

            • the issue is a proposed release blocker

            OpenShift On OpenStack added a comment - Removing the Triaged label because: the issue is a proposed release blocker

              maandre@redhat.com Martin André
              maandre@redhat.com Martin André
              Ramón Lobillo Ramón Lobillo
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: