Description of problem: $ oc get credentialsrequests -n openshift-cloud-credential-operator NAME AGE azure-openshift-ingress 24h cloud-credential-operator-iam-ro 24h gcp-openshift-ingress 24h openshift-image-registry 24h openshift-image-registry-azure 24h openshift-image-registry-gcs 24h openshift-image-registry-openstack 24h openshift-ingress 24h openshift-machine-api-aws 24h openshift-machine-api-azure 24h openshift-machine-api-gcp 24h openshift-machine-api-openstack 24h Version-Release number of selected component (if applicable): 4.2.0-0.nightly-2019-08-08-103722 How reproducible: 100% Steps to Reproduce: 1. Actual results: the name "azure-openshift-ingress" and "gcp-openshift-ingress" look different from other credentialsrequests name. Expected results: rename azure-openshift-ingress to openshift-ingress-azure rename gcp-openshift-ingress to openshift-ingress-gcp Additional info:
verified with 4.2.0-0.nightly-2019-08-14-211610 and issue has been fixed $ oc get credentialsrequests.cloudcredential.openshift.io -n openshift-cloud-credential-operator NAME AGE cloud-credential-operator-iam-ro 24m openshift-image-registry 24m openshift-image-registry-azure 24m openshift-image-registry-gcs 24m openshift-image-registry-openstack 24m openshift-ingress 24m openshift-ingress-azure 24m openshift-ingress-gcp 24m openshift-machine-api-aws 24m openshift-machine-api-azure 24m openshift-machine-api-gcp 24m openshift-machine-api-openstack 24m
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2922