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

api_server_api_priority_flowschema_catch_all fails on OpenShift 4.16

    XMLWordPrintable

Details

    Description

      Description of problem:

      The api_server_api_priority_flowschema_catch_all rule fails on OpenShift 4.16 clusters.  

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

      You can verify this using the ocp4-high profile with Compliance Operator 1.4.0 on OpenShift 4.16.

      How reproducible:

      100%

      Steps to Reproduce:

          1.Install the compliance operator 1.4.0
    2.Run the ocp4-high profile
    3.Observe api_server_api_priority_flowschema_catch_all failed when it is expected to pass    

      Actual results:

      Rule status is FAIL

      Expected results:

      Rule status should PASS

      Additional info:

      helpers.go:808: Result - Name: e2e-high-api-server-api-priority-flowschema-catch-all - Status: FAIL - Severity: medium
helpers.go:815: E2E-FAILURE: The expected result for the api_server_api_priority_flowschema_catch_all rule didn't match. Expected 'PASS', Got 'FAIL'

      Logs from https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/48091/rehearse-48091-periodic-ci-ComplianceAsCode-content-master-4.16-e2e-aws-ocp4-high-weekly/1753172697300340736

       

      Attachments

        Issue Links

          links to

          Web Link Adding v1 rule

          Web Link RHBA-2024:129828 openshift-compliance-operator bug fix and/or enhancement update

          Activity

            People

              wenshen@redhat.com Vincent Shen
              lbragsta@redhat.com Lance Bragstad
              Bhargavi Gudi Bhargavi Gudi
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated: