Cannot push images to GCR.

[drPytho]

Summary

The pipeline is trying to push images to GCR.

error pushing image: failed to push to destination gcr.io/project-id/test:0.0.0-SNAPSHOT-PR-2-3: DENIED: Token exchange failed for project 'project-id'. Caller does not have permission 'storage.buckets.get'. To configure permissions, follow instructions at: https://cloud.google.com/container-registry/docs/access-control

Steps to reproduce the behavior

Re-run the pipeline. /retest

Expected behavior

It manages to push the image

Actual behavior

It does not.

Jx version

NAME               VERSION
jx                 2.0.493
Kubernetes cluster v1.12.7-gke.25
kubectl            v1.15.0
helm client        Client: v2.14.2+ga8b13cc
git                git version 2.22.0
Operating System   Unkown Linux distribution Linux version 5.2.2-arch1-1-ARCH (builduser@heftig-71853) (gcc version 9.1.0 (GCC)) #1 SMP PREEMPT Sun Jul 21 19:18:34 UTC 2019

Jenkins type

jx install --provider=gke --ng --ingress-namespace=kube-system --ingress-deployment traefik-ingress-controller --ingress-service traefik-ingress-service --docker-registry eu.gcr.io --no-tiller --tekton --kaniko --docker-registry-org project-id

• Serverless Jenkins X Pipelines (Tekton + Prow)
• Classic Jenkins

Kubernetes cluster

GKE, created with gcloud. jx compliance was all good.

Operating system / Environment

Linux drHouse 5.2.2-arch1-1-ARCH #1 SMP PREEMPT Sun Jul 21 19:18:34 UTC 2019 x86_64 GNU/Linux

[drPytho]

Should I mount the SA key with https://jenkins-x.io/faq/pipelines/#how-do-i-mount-a-secret-or-configmap in each pipeline?

[martijnburger]

Same problem here, using jx boot.

[bbhuston]

Same problem here, using jx boot.

Ditto. Hitting same issue. Using fresh install of serverless jenkins X, using jx boot, and also used jx to create a GKE cluster from scratch.

NAME               VERSION
jx                 2.0.1094
Kubernetes cluster v1.14.8-gke.17
kubectl            v1.17.0
helm client        Client: v2.14.3+g0e7f3b6
git                2.21.0
Operating System   Mac OS X 10.12.6 build 16G2136

[jenkins-x-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

[jenkins-x-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

[jenkins-x-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

[jenkins-x-bot]

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.