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

All rhcos profiles return NOT-APPLICABLE for 4.19

XMLWordPrintable

    • Quality / Stability / Reliability
    • True
    • Hide

      Release blocker for Compliance Operator. It impacts scans for rhcos profiles

      Show
      Release blocker for Compliance Operator. It impacts scans for rhcos profiles
    • None
    • Important
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

       

      Description of problem:
      All rhcos profiles return NOT-APPLICABLE for 4.19
      It might related with https://github.com/openshift/installer/pull/9392 for https://issues.redhat.com//browse/COS-3014, OpenShift installer now uses pure RHEL bootimages. As a result, the worker os label has been updated from node.openshift.io/os_id=rhcos to node.openshift.io/os_id=rhel.
      % oc get node --show-labels -l node-role.kubernetes.io/worker=
      NAME               STATUS  ROLES  AGE  VERSION  LABELS
      xiyuan-19a-sxqx2-worker-a-lj8xj  Ready  worker  64m  v1.32.3  beta.kubernetes.io/arch=amd64,beta.kubernetes.io/instance-type=n2-standard-4,beta.kubernetes.io/os=linux,failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-a,kubernetes.io/arch=amd64,kubernetes.io/hostname=xiyuan-19a-sxqx2-worker-a-lj8xj,kubernetes.io/os=linux,node-role.kubernetes.io/worker=,node.kubernetes.io/instance-type=n2-standard-4,node.openshift.io/os_id=rhel,topology.gke.io/zone=us-central1-a,topology.kubernetes.io/region=us-central1,topology.kubernetes.io/zone=us-central1-a
      …
      When debugging on node, on a 4.19 cluster:
      sh-5.1# cat /etc/redhat-release 
      Red Hat Enterprise Linux release 9.6 (Plow)
      While on a 4.18 cluster:
      sh-5.1#  cat /etc/redhat-release 
      Red Hat Enterprise Linux CoreOS release 4.18    
      

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

      4.19 nightly payload    

      How reproducible:

      Always    

      Steps to Reproduce:

         1.Install Compliance Operator 
         2. Trigger a ssb with rhcos4-moderate profile        

      Actual results:

      The rhcos scans will return NOT-APPLICABLE for 4.19    

      Expected results:

      The scan for os should return COMPLIANT or NON-COMPLIANT     

      Additional info:

          

              wenshen@redhat.com Vincent Shen
              xiyuan@redhat.com Xiaojie Yuan
              None
              None
              Xiaojie Yuan Xiaojie Yuan
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: