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

Workload annotation missing in lvms namespace causing LVMS installation failure

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 1
    • Moderate
    • No
    • None
    • Proposed
    • OCPEDGE Sprint 248
    • 1
    • None
    • Release Note Not Required
    • N/A
    • None
    • None
    • None
    • None

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

       Setup OCP cluster with install-config having 'cpuPartitioningMode: AllNodes', when try to install lvms operator from operatorHub of OCP console UI, a default namespace "openshift-storage" gets automatically created and LVMS installation fails with below error,

install failed: deployment lvms-operator not ready before timeout: deployment "lvms-operator" exceeded its progress deadline

This is because, namespace "openshift-storage" which gets automatically created by console UI is missing 'workload.openshift.io/allowed: "management"' annotation.

After adding 'workload.openshift.io/allowed: "management"' annotation to lvms namespace (openshift-storage), LVMS operator get installed successfully.

       

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

          lvms 4.15.0-53

      How reproducible:

          Always

      Steps to Reproduce:

          1. Setup OCP cluster with install-config having cpuPartitioningMode: AllNodes     
    2. Search lvms operator from OperatorHub of OCP console UI
    3. Try installing LVMS with default 'openshift-storage' namespace
    4. Installation gets stuck and later fails with error: "install failed: deployment lvms-operator not ready before timeout: deployment "lvms-operator" exceeded its progress deadline"

      Actual results:

       "install failed: deployment lvms-operator not ready before timeout: deployment "lvms-operator" exceeded its progress deadline"    

      Expected results:

       LVMS operator should get installed successfully

      Additional info:

       This issue is only applicable when OCP cluster is setup with install-config having 'cpuPartitioningMode: AllNodes'

              sakbas@redhat.com Suleyman Akbas
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Rahul Deore Rahul Deore
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: