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

4.13 CRO unknown '-v' argument results in CrashLoopBackoff

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • None
    • 4.13
    • Pod Autoscaler
    • None
    • Important
    • No
    • 3
    • PODAUTO - Sprint 261
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      No release note needed per reporter.

      cluster-resource-override-admission no longer regards logging verbosity argument '-v' as unknown. The '-v' argument can once again be supplied and works properly to adjust verbosity level.
      Show
      No release note needed per reporter. cluster-resource-override-admission no longer regards logging verbosity argument '-v' as unknown. The '-v' argument can once again be supplied and works properly to adjust verbosity level.
    • Bug Fix
    • Done

      Description of problem:

          The dependency bump from https://github.com/openshift/cluster-resource-override-admission/pull/79 dragged in a generic-admission-server that does not properly initialize log flags, resulting in "unknown flag" when using a "-v" argument.

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

         clusterresourceoverride-operator.v4.13.0-202409120636

      How reproducible:

          Always on most recent 4.13

      Steps to Reproduce:

      1. Install newest 4.13 
2. Apply a CRO: 
apiVersion: operator.autoscaling.openshift.io/v1
kind: ClusterResourceOverride
metadata:
    name: cluster 
spec:
  podResourceOverride:
    spec:
      memoryRequestToLimitPercent: 50 
      cpuRequestToLimitPercent: 25 
      limitCPUToMemoryPercent: 200 
3. Watch the pods go into Error/CrashLoopBackoff:
[jkyros@jkyros-thinkpadp1gen5 cluster-resource-override-admission]$ oc get pods
NAME                                                READY   STATUS             RESTARTS      AGE
clusterresourceoverride-98mck                       0/1     CrashLoopBackOff   3 (32s ago)   82s
clusterresourceoverride-operator-86c5c67f8c-2qs9t   1/1     Running            0             101s
clusterresourceoverride-pnkxr                       0/1     CrashLoopBackOff   3 (32s ago)   82s
clusterresourceoverride-z9dq5                       0/1     CrashLoopBackOff   3 (32s ago)   82s

      Actual results:

          Pods fail because -v arg is unrecognized

      Expected results:

          Pods do not fail

      Additional info:

       

              jkyros@redhat.com John Kyros
              jkyros@redhat.com John Kyros
              Aditi Sahay Aditi Sahay
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: