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

openshift-manila-csi-driver is missing the workload.openshift.io/allowed label

XMLWordPrintable

    • +
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, the `openshift-manila-csi-driver` namespace did not include labels that are required for the management of workload partitioning. These missing labels can impact the operation of restricting Manila CSI pods to run on a selected set of CPUs. The {product-title} {product-version} fixes this issue in that the `openshift-manila-csi-driver` namespace now includes the `workload.openshift.io/allowed` label.(link:https://issues.redhat.com/browse/OCPBUGS-11341[*OCPBUGS-11341*])
      Show
      Previously, the `openshift-manila-csi-driver` namespace did not include labels that are required for the management of workload partitioning. These missing labels can impact the operation of restricting Manila CSI pods to run on a selected set of CPUs. The {product-title} {product-version} fixes this issue in that the `openshift-manila-csi-driver` namespace now includes the `workload.openshift.io/allowed` label.(link: https://issues.redhat.com/browse/OCPBUGS-11341 [* OCPBUGS-11341 *])
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-11112. The following is the description of the original issue:
      —
      Description of problem: The openshift-manila-csi-driver namespace should have the "workload.openshift.io/allowed= management" label.

      This is currently not the case:

      ❯ oc describe ns openshift-manila-csi-driver  
Name:         openshift-manila-csi-driver
Labels:       kubernetes.io/metadata.name=openshift-manila-csi-driver
              pod-security.kubernetes.io/audit=privileged
              pod-security.kubernetes.io/enforce=privileged
              pod-security.kubernetes.io/warn=privileged
Annotations:  include.release.openshift.io/self-managed-high-availability: true
              openshift.io/node-selector: 
              openshift.io/sa.scc.mcs: s0:c24,c4
              openshift.io/sa.scc.supplemental-groups: 1000560000/10000
              openshift.io/sa.scc.uid-range: 1000560000/10000
Status:       Active

No resource quota.

No LimitRange resource.

      It is causing CI jobs to fail with:

      {  fail [github.com/openshift/origin/test/extended/cpu_partitioning/platform.go:82]: projects [openshift-manila-csi-driver] do not contain the annotation map[workload.openshift.io/allowed:management]
Expected
    <[]string | len:1, cap:1>: [
        "openshift-manila-csi-driver",
    ]
to be empty
Ginkgo exit error 1: exit with code 1}

      For instance https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/27831/pull-ci-openshift-origin-release-4.13-e2e-openstack-ovn/1641317874201006080.

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

      How reproducible:

      Steps to Reproduce:

      1.
2.
3.

      Actual results:

      Expected results:

      Additional info:

              maandre@redhat.com Martin André
              openshift-crt-jira-prow OpenShift Prow Bot
              Yaakov Khodorkovski Yaakov Khodorkovski (Inactive)
              Darragh Fitzmaurice Darragh Fitzmaurice
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: