jx: Fails to promote to staging

I am running on minikube.

[web] Running shell script
++ cat ../../VERSION
+ jx promote -b --all-auto --timeout 1h --version 0.0.4
Promoting app tabletoprank-web version 0.0.4 to namespace jx-staging
Using pipeline: ****/tabletoprank-web/master build: #1
Cloning into '/home/jenkins/.jx/environments/****/environment-orioleazure-staging'...
Found remote branch names master, HEAD -> origin/master, master
Switched to branch 'promote-tabletoprank-web-0.0.4'
[promote-tabletoprank-web-0.0.4 3372b38] Promote tabletoprank-web to version 0.0.4
 1 file changed, 8 insertions(+), 5 deletions(-)
fatal: unable to get credential storage lock: Read-only file system
To https://github.com/****/environment-orioleazure-staging.git
 * [new branch]      HEAD -> promote-tabletoprank-web-0.0.4
Created Pull Request: https://github.com/****/environment-orioleazure-staging/pull/1

Using pipeline: ****/tabletoprank-web/master build: #1
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
WARNING: Failed to query the Pull Request last commit status for https://github.com/****/environment-orioleazure-staging/pull/1 ref 3372b38c983bac4d640b24969c90ace2cc4474ab Could not find a status for repository ****/environment-orioleazure-staging with ref 3372b38c983bac4d640b24969c90ace2cc4474ab
...

I think it is probably due to fatal: unable to get credential storage lock: Read-only file system

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 22 (10 by maintainers)

Most upvoted comments

I figured I’d try creating a cluster on GKE and seeing if I could get a build promoted but I still get an error. Here is the PR CI job build issue I am getting now when I run on GKE:

[-dragonglitter-staging_PR-1-EIWUC7VVN4N44PZJGX7JFP25OITEZW77LD6VRZ3OC3NXUQSYCC7A] Running shell script

+ make build

rm -rf requirements.lock

helm version

Client: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}

Server: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}

helm init

Creating /home/jenkins/.helm 

Creating /home/jenkins/.helm/repository 

Creating /home/jenkins/.helm/repository/cache 

Creating /home/jenkins/.helm/repository/local 

Creating /home/jenkins/.helm/plugins 

Creating /home/jenkins/.helm/starters 

Creating /home/jenkins/.helm/cache/archive 

Creating /home/jenkins/.helm/repository/repositories.yaml 

Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com 

Adding local repo with URL: http://127.0.0.1:8879/charts 

$HELM_HOME has been configured at /home/jenkins/.helm.

Warning: Tiller is already installed in the cluster.

(Use --client-only to suppress this message, or --upgrade to upgrade Tiller to the current version.)

Happy Helming!

helm repo add releases http://jenkins-x-chartmuseum:8080

"releases" has been added to your repositories

helm repo add jenkins-x http://chartmuseum.build.cd.jenkins-x.io

"jenkins-x" has been added to your repositories

helm dependency build "env"

Hang tight while we grab the latest from your chart repositories...

...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879/charts):

	Get http://127.0.0.1:8879/charts/index.yaml: dial tcp 127.0.0.1:8879: getsockopt: connection refused

...Successfully got an update from the "releases" chart repository

...Successfully got an update from the "stable" chart repository

...Successfully got an update from the "jenkins-x" chart repository

Update Complete. ⎈Happy Helming!⎈

Error: tabletoprank-web chart not found in repo http://jenkins-x-chartmuseum:8080

make: *** [build] Error 1

script returned exit code 2

The charts are showing up in monocular, but it appears that there is an issue pulling the chart. The chart is named ‘web’ in monocular, but it seems from the error message that it is looking for a chart named ‘tabletoprank-web’, which is the name of my github repo, while ‘web’, is the name of my local git repo.

camusd on Mar 25, 2018

@gauravnavgire @eecarus @odzhu @camusd I’ve just fixed this issue: #674 so that if, for whatever reason, webhooks are not working/configured/allowed through your firewall, then promotion should still work (albeit slow - it polls every 5 minutes for pending Pull Requests / merges to master)

To try out this fix you can run this:

jx upgrade cli

which should upgrade your jx version to at least 1.2.8 or later to get this fix.

Then either re-create a Jenkins X cluster from scratch or:

delete your environments via:

jx delete env staging
jx delete env production

Then remove the jobs from jenkins in the UI

jx console

Then recreate the Environments again:

jx create env staging
....
jx create env production
....

then the new projects for the environments should have a background poll of 5 minutes applied. (You can always edit this time to shorter in the Jenkins UI if you Configure the environment projects in the Jenkins UI)

jstrachan on Apr 19, 2018

@gauravnavgire see my comment above. Could you see if the Pull Request build has been triggered in Jenkins? It could be lack of resources or that webhooks are not working.

jstrachan on Apr 19, 2018