Bug 1795312

Summary:	oc: error: No Auth Provider found for name "gcp"
Product:	OpenShift Container Platform	Reporter:	Maciej Szulik <maszulik>
Component:	oc	Assignee:	Maciej Szulik <maszulik>
Status:	CLOSED ERRATA	QA Contact:	Steve Kuznetsov <skuznets>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	aos-bugs, deads, jokerman, maszulik, mfojtik, skuznets, vlaad, yinzhou
Target Milestone:	---
Target Release:	4.2.z
Hardware:	Unspecified
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	1795302	Environment:
Last Closed:	2020-05-13 11:07:17 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1795302
Bug Blocks:

Description Maciej Szulik 2020-01-27 16:38:26 UTC

+++ This bug was initially created as a clone of Bug #1795302 +++

+++ This bug was initially created as a clone of Bug #1794516 +++

Configure a GKE cluster auth in a config:

$ yq .users[0] < ~/.kube/prow
users:
- name: gke_k8s-prow-builds_us-central1-f_prow
  user:
    auth-provider:
      config:
        access-token: xxx
        cmd-args: config config-helper --format=json
        cmd-path: /home/skuznets/google-cloud-sdk/bin/gcloud
        expiry: "2019-08-06T18:08:09Z"
        expiry-key: '{.credential.token_expiry}'
        token-key: '{.credential.access_token}'
      name: gcp

Run a command:

$ KUBECONFIG=~/.kube/prow kubectl get pods
error: No Auth Provider found for name "gcp"


$ oc version
Client Version: v4.2.14
Kubernetes Version: v1.11.0+d4cacc0

Comment 6 Steve Kuznetsov 2020-05-11 14:53:48 UTC

This works as expected!

Comment 8 errata-xmlrpc 2020-05-13 11:07:17 UTC

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-2020:2023