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

namespace "openshift-cluster-api" not found in CustomNoUpgrade

    • No
    • CLOUD Sprint 249
    • 1
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      Description of problem:

          capi-based installer failing with missing openshift-cluster-api namespace

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

          

      How reproducible:

      Always in CustomNoUpgrade

      Steps to Reproduce:

          1.
          2.
          3.
          

      Actual results:

          Install failure

      Expected results:

          namespace create, install succeeds or does not error on missing namespace

      Additional info:

          

            [OCPBUGS-29676] namespace "openshift-cluster-api" not found in CustomNoUpgrade

            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

            Moving to verified as this was pre-merge-tested

            Damiano Donati added a comment - Moving to verified as this was pre-merge-tested

            After discussing with ddonati@redhat.com , the issue is not related to the change , adding pre-merge-tested label 

            test case

            Milind Yadav added a comment - After discussing with ddonati@redhat.com , the issue is not related to the change , adding pre-merge-tested label  test case

            I see network co degraded, not sure if they are related . 

            [miyadav@miyadav ~]$ oc describe co network 
            Name:         network
            Namespace:    
            Labels:       <none>
            Annotations:  include.release.openshift.io/ibm-cloud-managed: true
                          include.release.openshift.io/self-managed-high-availability: true
                          include.release.openshift.io/single-node-developer: true
                          network.operator.openshift.io/last-seen-state: {"DaemonsetStates":[],"DeploymentStates":[],"StatefulsetStates":[]}
                          network.operator.openshift.io/relatedClusterObjects: 
            API Version:  config.openshift.io/v1
            Kind:         ClusterOperator
            Metadata:
              Creation Timestamp:  2024-02-20T09:59:55Z
              Generation:          1
              Owner References:
                API Version:     config.openshift.io/v1
                Controller:      true
                Kind:            ClusterVersion
                Name:            version
                UID:             a48bb3de-5e4f-4ad5-adf6-9d8325ebf0bd
              Resource Version:  56625
              UID:               6ad57813-d840-4cdc-93d8-b7d56db8c5e0
            Spec:
            Status:
              Conditions:
                Last Transition Time:  2024-02-20T10:58:04Z
                Message:               Panic detected: feature "AdminNetworkPolicy" is not registered in FeatureGates []
             

            must-gather - https://drive.google.com/file/d/10bz9pRr3mpmiLFIOXooEKF0qJSDzAfzs/view?usp=sharing

            Milind Yadav added a comment - I see network co degraded, not sure if they are related .  [miyadav@miyadav ~]$ oc describe co network  Name:         network Namespace:     Labels:       <none> Annotations:  include.release.openshift.io/ibm-cloud-managed: true               include.release.openshift.io/self-managed-high-availability: true               include.release.openshift.io/single-node-developer: true               network. operator .openshift.io/last-seen-state: { "DaemonsetStates" :[], "DeploymentStates" :[], "StatefulsetStates" :[]}               network. operator .openshift.io/relatedClusterObjects:  API Version:  config.openshift.io/v1 Kind:         ClusterOperator Metadata:   Creation Timestamp:  2024-02-20T09:59:55Z   Generation:          1   Owner References:     API Version:     config.openshift.io/v1     Controller:       true     Kind:            ClusterVersion     Name:            version     UID:             a48bb3de-5e4f-4ad5-adf6-9d8325ebf0bd   Resource Version:  56625   UID:               6ad57813-d840-4cdc-93d8-b7d56db8c5e0 Spec: Status:   Conditions:     Last Transition Time:  2024-02-20T10:58:04Z     Message:               Panic detected: feature "AdminNetworkPolicy" is not registered in FeatureGates [] must-gather - https://drive.google.com/file/d/10bz9pRr3mpmiLFIOXooEKF0qJSDzAfzs/view?usp=sharing

            Joseph Callen added a comment - - edited

            Joseph Callen added a comment - - edited slack thread: https://redhat-internal.slack.com/archives/C05QFJN2BQW/p1708352870908829   Both vSphere and OpenStack platforms are experiencing this problem https://prow.ci.openshift.org/?type=periodic&job=*capi*&cluster=vsphere02

              ddonati@redhat.com Damiano Donati
              jcallen@redhat.com Joseph Callen
              Milind Yadav Milind Yadav
              Jeana Routh Jeana Routh
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: