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

"oc prune renderedmachineconfigs" should be consistent when reporting failures when using wrong pool names

XMLWordPrintable

    • +
    • Moderate
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Inconsitent behaviour when we provide invalid pool names

$ oc adm prune renderedmachineconfigs list  --pool-name fake
$ echo $?
0
$ oc adm prune renderedmachineconfigs list --in-use --pool-name fake
error: MachineConfigPool with name 'fake' not found
$ echo $?
1

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

      How reproducible:

      Always

      Steps to Reproduce:

      $ oc adm prune renderedmachineconfigs list  --pool-name fake
$ echo $?
0
$ oc adm prune renderedmachineconfigs list --in-use --pool-name fake
error: MachineConfigPool with name 'fake' not found
$ echo $?
1

      Actual results:

      We should give a consistent response when the user tries to use pools that do not exist.

      Expected results:

      Similar behaviour when we use wrong pool names in the "oc adm renderedmachineconfig" commands.

      Additional info:

              rhn-support-cruhm Courtney Ruhm
              sregidor@redhat.com Sergio Regidor de la Rosa
              Sergio Regidor de la Rosa Sergio Regidor de la Rosa
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: