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

Baremetal operator not rolled out after installing OCP 4.8.2 using single-node-developer profile

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 4.8
    • crc
    • Quality / Stability / Reliability
    • None
    • None
    • None
    • None
    • None
    • Unspecified
    • None
    • None
    • None
    • None
    • None
    • If docs needed, set a value
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      Installed OCP 4.8.2 using the single-node-developer profile:

      $ export OPENSHIFT_INSTALL_EXPERIMENTAL_CLUSTER_PROFILE=single-node-developer
      $ oc create manifests
      $ oc create ignition-configs

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

      4.8.2, link https://mirror.openshift.com/pub/openshift-v4/clients/ocp/4.8.2/

      How reproducible:

      Just install OpenShift 4.8.2 using the single-node-developer profile

      Actual results:

      The kube-apiserver operator remains in a degraded state:

      $ oc get clusteroperator
      NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE
      authentication 4.8.2 True False False 23m
      baremetal
      cluster-autoscaler 4.8.2 True False False 39m
      config-operator 4.8.2 True False False 40m
      console 4.8.2 False False False 32m
      csi-snapshot-controller 4.8.2 True False False 40m
      dns 4.8.2 True False False 40m
      etcd 4.8.2 True False False 39m
      image-registry 4.8.2 True False False 33m
      ingress 4.8.2 True False False 34m
      insights 4.8.2 True False False 33m
      kube-apiserver 4.8.2 True False True 35m
      kube-controller-manager 4.8.2 True False False 39m
      kube-scheduler 4.8.2 True False False 36m
      machine-api 4.8.2 True False False 39m
      machine-approver 4.8.2 True False False 40m
      machine-config 4.8.2 True False False 39m
      marketplace 4.8.2 True False False 39m
      monitoring 4.8.2 True False False 31m
      network 4.8.2 True False False 41m
      node-tuning 4.8.2 True False False 39m
      openshift-apiserver 4.8.2 True False False 33m
      openshift-controller-manager 4.8.2 True False False 39m
      openshift-samples 4.8.2 True False False 32m
      operator-lifecycle-manager 4.8.2 True False False 40m
      operator-lifecycle-manager-catalog 4.8.2 True False False 40m
      operator-lifecycle-manager-packageserver 4.8.2 True False False 33m
      service-ca 4.8.2 True False False 40m
      storage 4.8.2 True False False 40m

      Expected results:

      Baremetal operator fails to roll out.

      Additional info:

      This issue is caused by the cluster-version operator not deploying 0000_31_cluster-baremetal-operator_03_service.yaml resource.

      This is the command that fixes the issue for me:

      $ oc rsh -n openshift-cluster-version cluster-version-operator-789d46ff9d-jqbgt cat /release-manifests/0000_31_cluster-baremetal-operator_03_service.yaml | oc apply -f -

      This issue is similar to https://bugzilla.redhat.com/show_bug.cgi?id=1986129

              prkumar@redhat.com Praveen Kumar
              anosek@redhat.com Ales Nosek
              None
              None
              Tomáš Sedmík Tomáš Sedmík
              Kevin Owen Kevin Owen
              Red Hat Employee
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: