version False True 55m Unable to apply 4.2.0-0.okd-2019-07-26-174449: some cluster operators have not yet rolled out $ oc get clusteroperator | grep -E 'cloud|ingress' cloud-credential 4.2.0-0.okd-2019-07-26-174449 True True False 53m ingress 4.2.0-0.okd-2019-07-26-174449 True False False 17m Ingress is failing because it hasn't gotten a cred it asked for. Cred is saying (for hours): - lastTransitionTime: "2019-07-26T18:17:33Z" message: 0 of 1 credentials requests provisioned, 0 reporting errors. reason: Reconciling status: "True" type: Progressing Then I look in the cloud-cred-op logs: time="2019-07-26T19:05:50Z" level=debug msg="syncing cluster operator status" time="2019-07-26T19:05:50Z" level=debug msg="1 cred requests" time="2019-07-26T19:05:50Z" level=debug msg="set ClusterOperator condition" message="No credentials requests reporting errors." reason=NoCredentialsFailing status=False type=Degraded time="2019-07-26T19:05:50Z" level=debug msg="set ClusterOperator condition" message="0 of 1 credentials requests provisioned, 0 reporting errors." reason=Reconciling status=True type=Progressing time="2019-07-26T19:05:50Z" level=debug msg="set ClusterOperator condition" message= reason= status=True type=Available time="2019-07-26T19:05:50Z" level=debug msg="set ClusterOperator condition" message= reason= status=True type=Upgradeable time="2019-07-26T19:12:04Z" level=info msg="syncing credentials request" controller=credreq cr=openshift-cloud-credential-operator/openshift-machine-api time="2019-07-26T19:12:04Z" level=debug msg="ignoring cr as it is for a different cloud" controller=credreq cr=openshift-cloud-credential-operator/openshift-machine-api secret=openshift-machine-api/aws-cloud-credentials time="2019-07-26T19:12:04Z" level=debug msg="updating credentials request status" controller=credreq cr=openshift-cloud-credential-operator/openshift-machine-api secret=openshift-machine-api/aws-cloud-credentials time="2019-07-26T19:12:04Z" level=debug msg="status unchanged" controller=credreq cr=openshift-cloud-credential-operator/openshift-machine-api secret=openshift-machine-api/aws-cloud-credentials time="2019-07-26T19:12:04Z" level=debug msg="syncing cluster operator status" time="2019-07-26T19:12:04Z" level=debug msg="1 cred requests" time="2019-07-26T19:12:04Z" level=debug msg="set ClusterOperator condition" message="No credentials requests reporting errors." reason=NoCredentialsFailing status=False type=Degraded time="2019-07-26T19:12:04Z" level=debug msg="set ClusterOperator condition" message="0 of 1 credentials requests provisioned, 0 reporting errors." reason=Reconciling status=True type=Progressing time="2019-07-26T19:12:04Z" level=debug msg="set ClusterOperator condition" message= reason= status=True type=Available time="2019-07-26T19:12:04Z" level=debug msg="set ClusterOperator condition" message= reason= status=True type=Upgradeable time="2019-07-26T19:12:07Z" level=info msg="syncing credentials request" controller=credreq cr=openshift-cloud-credential-operator/openshift-machine-api time="2019-07-26T19:12:07Z" level=debug msg="ignoring cr as it is for a different cloud" controller=credreq cr=openshift-cloud-credential-operator/openshift-machine-api secret=openshift-machine-api/openstack-cloud-credentials time="2019-07-26T19:12:07Z" level=debug msg="updating credentials request status" controller=credreq cr=openshift-cloud-credential-operator/openshift-machine-api secret=openshift-machine-api/openstack-cloud-credentials time="2019-07-26T19:12:07Z" level=debug msg="status unchanged" controller=credreq cr=openshift-cloud-credential-operator/openshift-machine-api secret=openshift-machine-api/openstack-cloud-credentials
I just built a new installer from master, and spun up a GCP cluster. While ingress isn't coming up (I didn't investigate why), I do see that the credentials for ingress have been provisioned successfully. Specifically, here you can see the CredentialsRequest for ingress has been provisioned: [jdiaz@minigoomba bin (master $%=)]$ oc --config ./auth/kubeconfig get credentialsrequests -n openshift-cloud-credential-operator gcp-openshift-ingress -o json | jq -r .status.provisioned true And the secret exists where one would expect (ie openshift-ingress-operator/cloud-credentials): [jdiaz@minigoomba bin (master $%=)]$ oc --config ./auth/kubeconfig get credentialsrequests -n openshift-cloud-credential-operator gcp-openshift-ingress -o json | jq -r .spec.secretRef { "name": "cloud-credentials", "namespace": "openshift-ingress-operator" } [jdiaz@minigoomba bin (master $%=)]$ oc --config ./auth/kubeconfig get secret -n openshift-ingress-operator cloud-credentials NAME TYPE DATA AGE cloud-credentials Opaque 1 33m [jdiaz@minigoomba bin (master $%=)]$ The above was with version 4.2.0-0.okd-2019-08-06-174958. Can you verify that these credentials do get provisioned with newer installs on GCP?
after discussion with Jeff, we can just start moving this through to verified fixed with current versions.
Verified on 4.2.0-0.nightly-2019-08-08-032431 [onest@localhost hive]$ oc get clusteroperator cloud-credential -o yaml apiVersion: config.openshift.io/v1 kind: ClusterOperator metadata: creationTimestamp: "2019-08-08T08:58:50Z" generation: 1 name: cloud-credential resourceVersion: "4156" selfLink: /apis/config.openshift.io/v1/clusteroperators/cloud-credential uid: bd9a83a3-b9ba-11e9-bf86-0ea8dc383be4 spec: {} status: conditions: - lastTransitionTime: "2019-08-08T08:59:26Z" message: No credentials requests reporting errors. reason: NoCredentialsFailing status: "False" type: Degraded - lastTransitionTime: "2019-08-08T08:59:26Z" message: 4 of 4 credentials requests provisioned and reconciled. reason: ReconcilingComplete status: "False" type: Progressing - lastTransitionTime: "2019-08-08T08:58:50Z" status: "True" type: Available - lastTransitionTime: "2019-08-08T08:58:50Z" status: "True" type: Upgradeable extension: null relatedObjects: - group: "" name: openshift-cloud-credential-operator resource: namespaces versions: - name: operator version: 4.2.0-0.nightly-2019-08-08-032431 logs from cloud-credential-operator pod time="2019-08-08T09:39:19Z" level=debug msg="syncing cluster operator status" time="2019-08-08T09:39:19Z" level=debug msg="4 cred requests" time="2019-08-08T09:39:19Z" level=debug msg="set ClusterOperator condition" message="No credentials requests reporting errors." reason=NoCredentialsFailing status=False type=Degraded time="2019-08-08T09:39:19Z" level=debug msg="set ClusterOperator condition" message="4 of 4 credentials requests provisioned and reconciled." reason=ReconcilingComplete status=False type=Progressing time="2019-08-08T09:39:19Z" level=debug msg="set ClusterOperator condition" message= reason= status=True type=Available time="2019-08-08T09:39:19Z" level=debug msg="set ClusterOperator condition" message= reason= status=True type=Upgradeable time="2019-08-08T09:39:19Z" level=info msg="syncing credentials request" controller=credreq cr=openshift-cloud-credential-operator/openshift-image-registry-openstack
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