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

Rule ocp4-api-server-encryption-provider-cipher return fail while it should PASS on a aws-ipi-ovn-hypershift-mce mgmt cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 4.13.z
    • Compliance Operator
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • No
    • None
    • None
    • CMP Sprint 68, CMP Sprint 69
    • 2
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      When scanning from mgmt cluster on a aws-ipi-ovn-hypershift-mce cluster, rule ocp4-api-server-encryption-provider-cipher return FAIL while it should PASS. $ oc get ccr -l compliance.openshift.io/check-status=FAIL
      $ oc get ccr -l compliance.openshift.io/check-status=FAIL
      NAME                                                             STATUS   SEVERITY
      hypershift-cismzv9kys8g7-api-server-encryption-provider-cipher   FAIL     medium
      hypershift-cismzv9kys8g7-audit-log-forwarding-enabled            FAIL     medium
      hypershift-cismzv9kys8g7-configure-network-policies-namespaces   FAIL     high
      hypershift-cismzv9kys8g7-idp-is-configured                       FAIL     medium
      hypershift-cismzv9kys8g7-kubeadmin-removed                       FAIL     medium
      hypershift-cismzv9kys8g7-ocp-api-server-audit-log-maxbackup      FAIL     low
      $ oc get --raw  /apis/hypershift.openshift.io/v1beta1/namespaces/local-cluster/hostedclusters/acfd5e74e18f6cb76f95 | jq [.spec.secretEncryption.type]
      [
        "aescbc"
      ]
      

       

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

      4.13.z

      How reproducible:

      Always on a aws-ipi-ovn-hypershift-mce cluster

      Steps to Reproduce:

       

      1. Install Compliance Operator 
      2. Create a tp use below yaml file:
      $ oc apply -f -<<EOF
      apiVersion: compliance.openshift.io/v1alpha1
      kind: TailoredProfile
      metadata:
        name: hypershift-cismzv9kys8g7
        namespace: openshift-compliance
      spec:
        description: This profile test required rules
        extends: ocp4-cis
        setValues:
        - name: ocp4-hypershift-cluster
          rationale: This value is used for HyperShift version detection
          value: acfd5e74e18f6cb76f95
        - name: ocp4-hypershift-namespace-prefix
          rationale: This value is used for HyperShift controlplane namespace detection
          value: local-cluster
        title: My little profile
      $ oc get tp
      NAME                           STATE
      hypershift-cismzv9kys8g7       READY
       
      3. Create a ssb:
      $ oc compliance bind -N test tailoredprofile/hypershift-pci-dssmzv9kys8g7
      Creating ScanSettingBinding test
       
      

      Actual results:

      Rule ocp4-api-server-encryption-provider-cipher return FAIL.

      Expected results:

      Rule ocp4-api-server-encryption-provider-cipher should PASS.

      Additional info:

      It only reproduced on a aws-ipi-ovn-hypershift-mce cluster

              wsato@redhat.com Watson Sato
              xiyuan@redhat.com Xiaojie Yuan
              None
              None
              Xiaojie Yuan Xiaojie Yuan
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: