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

SR-IOV: Unable to Recreate Default SriovOperatorConfig

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 4.17.0
    • Networking / SR-IOV
    • None
    • Moderate
    • No
    • CNF Network Sprint 262
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      Cause – When the user deletes the default SriovOperatorConfig resource to disable the operator, the webhook service is deleted but the ValidatingWebhookConfiguration is still present in the cluster.
      Consequence – The user can't recreate the default SriovOperatorConfig resource, as the validation webhook is not working.
      Fix – When the SriovOperatorConfig resource is deleted, the operator deletes the ValidatingWebhookConfiguration.
      Result – The user can recreate SriovOperatorConfig resources and get the operator up and running.
      Show
      Cause – When the user deletes the default SriovOperatorConfig resource to disable the operator, the webhook service is deleted but the ValidatingWebhookConfiguration is still present in the cluster. Consequence – The user can't recreate the default SriovOperatorConfig resource, as the validation webhook is not working. Fix – When the SriovOperatorConfig resource is deleted, the operator deletes the ValidatingWebhookConfiguration. Result – The user can recreate SriovOperatorConfig resources and get the operator up and running.
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-43108. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-41897. The following is the description of the original issue:
      —
      Description of problem:
      Unable to Recreate Default SriovOperatorConfig

      Version-Release number of selected component (if applicable):
      4.17.0-rc.2
      sriov-network-operator.v4.17.0-202409100034

      How reproducible:

      100%

      Steps to Reproduce:

      • Apply the default SriovOperatorConfig.
      • Remove the default SriovOperatorConfig.
      • Apply it again.

      Actual results:

      $ oc apply -f /tmp/opconfig.yml Error from server (InternalError): error when creating "/tmp/opconfig.yml": Internal error occurred: failed calling webhook "operator-webhook.sriovnetwork.openshift.io": failed to call webhook: Post "https://operator-webhook-service.openshift-sriov-network-operator.svc:443/validating-custom-resource?timeout=10s": service "operator-webhook-service" not found

      Expected results:
      Recreated successfully

      Additional info:

              bnemeth@redhat.com Balazs Nemeth
              openshift-crt-jira-prow OpenShift Prow Bot
              Zhanqi Zhao Zhanqi Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: