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

Configuring IAM for Nutanix provides incorrect command to extract credential requests CR

XMLWordPrintable

    • No
    • 1
    • OSDOCS Sprint 250
    • 1
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required

      Description of problem:

      When trying to configure the nutanix IAM, it is not quite clear the 'path' referring to what especially for the quay.io for the command below. 
      
      oc adm release extract --credentials-requests --cloud=nutanix \//
      --to=<path_to_directory_with_list_of_credentials_requests>/credrequests \ 
      quay.io/<path_to>/ocp-release:<version>
      
      
      [1] https://docs.openshift.com/container-platform/4.11/installing/installing_nutanix/installing-nutanix-installer-provisioned.html#manually-create-iam-nutanix_installing-nutanix-installer-provisioned
      

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

       

      How reproducible:

      100%

      Steps to Reproduce:

      1. N/A
      2.
      3.
      

      Actual results:

      credential requests CR command is incorrect

      Expected results:

      provide complete information

      Additional info:

      The following command can work in place of the existing command
      
      ~~~
      oc adm release extract --credentials-requests --cloud=nutanix \//
      --to=<path_to_directory_with_list_of_credentials_requests>/credrequests \ 
      quay.io/openshift-release-dev/ocp-release:<version>
      ~~~
      
      This also works,
      
      ~~~
      oc adm release extract quay.io/openshift-release-dev/ocp-release:4.y.z-x86_64 \
        --credentials-requests \
        --cloud=nutanix
      ~~~

              jrouth@redhat.com Jeana Routh
              rhn-support-chdeshpa Chinmay Deshpande
              Jianping Shu Jianping Shu
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: