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

Incorrect help info for loglevel when using --v2 flag

XMLWordPrintable

    • Important
    • None
    • CLID Sprint 251, CLID Sprint 252, CLID Sprint 253
    • 3
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required
    • In Progress
    • Customer Facing

      Description of problem:

      Incorrect help info for loglevel when using --v2 flag 

       

       

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

      oc-mirror version 
      WARNING: This version information is deprecated and will be replaced with the output from --short. Use --output=yaml|json to get the full version.
      Client Version: version.Info{Major:"", Minor:"", GitVersion:"4.16.0-202403070215.p0.gc4f8295.assembly.stream.el9-c4f8295", GitCommit:"c4f829512107f7d0f52a057cd429de2030b9b3b3", GitTreeState:"clean", BuildDate:"2024-03-07T03:46:24Z", GoVersion:"go1.21.7 (Red Hat 1.21.7-1.el9) X:strictfipsruntime", Compiler:"gc", Platform:"linux/amd64"}

      How reproducible:

      always

      Steps to Reproduce:

      1) Check `oc-mirror –v2 -h` help info
      2) When use command `oc-mirror --config config.yaml --from file://out docker://xxxxxx.com:5000/test  --v2 --max-nested-paths 2 --loglevel trace`
      

      Actual results: 

      oc-mirror --config config.yaml --from file://out docker://ec2-18-188-118-33.us-east-2.compute.amazonaws.com:5000/test  --v2 --max-nested-paths 2 --loglevel trace
      --v2 flag identified, flow redirected to the oc-mirror v2 version. PLEASE DO NOT USE that. V2 is still under development and it is not ready to be used. 
      2024/03/20 07:18:30  [INFO]   : mode diskToMirror 
      2024/03/20 07:18:30  [TRACE]  : creating signatures directory out/working-dir/signatures 
      2024/03/20 07:18:30  [TRACE]  : creating release images directory out/working-dir/release-images 
      2024/03/20 07:18:30  [TRACE]  : creating release cache directory out/working-dir/hold-release 
      2024/03/20 07:18:30  [TRACE]  : creating operator cache directory out/working-dir/hold-operator 
      2024/03/20 07:18:30  [ERROR]  :  error parsing local storage configuration : invalid loglevel trace Must be one of [error, warn, info, debug]
      

      Expected results:

      Show correct help information

       

      Additional info:

      same for `--strict-archive archiveSize`, the information is not clear how to use it.

            skhoury@redhat.com Sherine Khoury
            yinzhou@redhat.com ying zhou
            ying zhou ying zhou
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: