[JIRA] (JENKINS-58837) withDockerRegistry on multiple clusters
Title: Message Title pjdarton commented on JENKINS-58837 Re: withDockerRegistry on multiple clusters FYI withDockerRegistry etc come from the docker-workflow-plugin, not the docker-plugin. I've updated the components field accordingly. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201152.1565148699000.4150.1569327840380%40Atlassian.JIRA.
[JIRA] (JENKINS-58837) withDockerRegistry on multiple clusters
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-58837 withDockerRegistry on multiple clusters Change By: pjdarton Component/s: docker-workflow-plugin Component/s: docker-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201152.1565148699000.4145.1569327720237%40Atlassian.JIRA.
[JIRA] (JENKINS-58837) withDockerRegistry on multiple clusters
Title: Message Title Paul Clark commented on JENKINS-58837 Re: withDockerRegistry on multiple clusters Workaround: Command line docket logins, do the image mirror and then Docker logouts Post pipeline always to empty out the docker config.json. Not the best as any other pipelines running at the same time for cluster promotions on that node would have issues Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201152.1565148699000.217.1566848703479%40Atlassian.JIRA.
[JIRA] (JENKINS-58837) withDockerRegistry on multiple clusters
Title: Message Title Sergey Gladskih edited a comment on JENKINS-58837 Re: withDockerRegistry on multiple clusters Today I faced exactly the same bug. At least it's not the a problem of Windows agent that I use. Did you find some workaround (except traditional pull + push)? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201152.1565148699000.10058.1566835320143%40Atlassian.JIRA.
[JIRA] (JENKINS-58837) withDockerRegistry on multiple clusters
Title: Message Title Sergey Gladskih commented on JENKINS-58837 Re: withDockerRegistry on multiple clusters Today I faced exactly the same bug. At least it's not the problem of Windows agent that I use. Did you find some workaround (except traditional pull + push)? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201152.1565148699000.10055.1566835260188%40Atlassian.JIRA.
[JIRA] (JENKINS-58837) withDockerRegistry on multiple clusters
Title: Message Title
Paul Clark updated an issue
Jenkins / JENKINS-58837
withDockerRegistry on multiple clusters
Change By:
Paul Clark
Following instructions on [https://github.com/openshift/jenkins-client-plugin#moving-images-cluster-to-cluster], I am unable to promote the image between two openshift clusters as it throws an authentication issue.Adding a sleep after the two withDockerRegistry calls, I can see that two folders are created under the @TMP directory (unique names for each) with a config.json under each of them - these contain the authentication details to the respective registries. Docker-commons-plugin version: 1.15Docker plugin version: 1.1.7Openshift Client plugin version: 1.0.31 (openshift client and docker registry version: 3.7.119)Jenkins: 2.176.2 {code:java} [Pipeline] { (Copy from source to dest) [Pipeline] script [Pipeline] { [Pipeline] withDockerRegistry $ docker login -u openshift/skopeo -p [ https://docker-registry-default. |https://docker-registry-default.infra.ocp-reg.hbs.net.au/] Login Succeeded [Pipeline] { [Pipeline] withDockerRegistry $ docker login -u ci-cd/jenkins -p [ https://docker-registry. |https://docker-registry.apps.ocp-tst.hbs.net.au/] Login Succeeded [Pipeline] { [Pipeline] sh + /bin/oc image mirror --insecure=true docker-registry./appversion/appversion:latest docker-registry-default./appversion/appversion:latesterror: unable to retrieve source image docker-registry./appversion/appversion by tag: unauthorized: authentication required [Pipeline] } [Pipeline] // withDockerRegistry [Pipeline] } [Pipeline] // withDockerRegistry [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of PipelineERROR: script returned exit code 1Finished: FAILURE{code}
Add Comment
[JIRA] (JENKINS-58837) withDockerRegistry on multiple clusters
Title: Message Title
Paul Clark created an issue
Jenkins / JENKINS-58837
withDockerRegistry on multiple clusters
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
docker-commons-plugin, docker-plugin, openshift-client-plugin
Created:
2019-08-07 03:31
Priority:
Minor
Reporter:
Paul Clark
Following instructions on https://github.com/openshift/jenkins-client-plugin#moving-images-cluster-to-cluster, I am unable to promote the image between two openshift clusters as it throws an authentication issue. Adding a sleep after the two withDockerRegistry calls, I can see that two folders are created under the @TMP directory (unique names for each) with a config.json under each of them - these contain the authentication details to the respective registries. Docker-commons-plugin version: 1.15 Docker plugin version: 1.1.7 Openshift Client plugin version: 1.0.31 (openshift client and docker registry version: 3.7.119) Jenkins: 2.176.2 [Pipeline] { (Copy from source to dest)[Pipeline] script[Pipeline] {[Pipeline] withDockerRegistry$ docker login -u openshift/skopeo -p https://docker-registry-default.Login Succeeded[Pipeline] {[Pipeline] withDockerRegistry$ docker login -u ci-cd/jenkins -p https://docker-registry.Login Succeeded[Pipeline] {[Pipeline] sh+ /bin/oc image mirror --insecure=true docker-registry./appversion/appversion:latest docker-registry-default./appversion/appversion:latest error: unable to retrieve source image docker-registry./appversion/appversion by tag: unauthorized: authentication required[Pipeline] } [Pipeline] // withDockerRegistry[Pipeline] }[Pipeline] // withDockerRegistry[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // node
