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

oc get dc fails when AllRequestBodies audit-profile is set in apiserver

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • 4.12.z
    • 4.10.z
    • openshift-apiserver
    • Moderate
    • False
    • Hide

      None

      Show
      None

      This is a clone of issue OCPBUGS-501. The following is the description of the original issue:

      Description of problem: 

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

      How reproducible: Always

      Steps to Reproduce:
      1. Edit the apiserver resource and add spec.audit.customRules field

      $ oc get apiserver cluster -o yaml
      spec:
      audit:
      customRules:

      • group: system:authenticated:oauth
        profile: AllRequestBodies
      • group: system:authenticated
        profile: AllRequestBodies
        profile: Default

      2. Allow the kube-apiserver pods to rollout new revision.
      3. Once the kube-apiserver pods are in new revision execute $ oc get dc

      Actual results:

      Error from server (InternalError): an error on the server ("This request caused apiserver to panic. Look in the logs for details.") has prevented the request from succeeding (get deploymentconfigs.apps.openshift.io)

      Expected results: The command "oc get dc" should display the deploymentconfig without any error.

      Additional info:

            Unassigned Unassigned
            openshift-crt-jira-prow OpenShift Prow Bot
            Rahul Gangwar Rahul Gangwar
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: