we are not seeing problems now...
you see that SHA from the image streams section?
a5e6198049fd2abc261ecb06cdbe66e478af328ad01bb3356c4aef4698c90ba7
-- Scott Hebert Software Engineering
On Tue, Sep 26, 2017 at 9:41 AM, Anton Sherkhonov asherkho@redhat.com wrote:
thanks,
Looks like the problem is deeper. Does anyone have images pulling successfully? can someone possibly check on docker well being on the node: n11.humpty.ci.centos.org ? Specifically whether it can pull from the internal registry.
10s 10s 1 {kubelet n11.humpty.ci.centos.org} spec.containers{shipshift- worker} Normal Pulling pulling image "172.30.254.79:5000/shipshift/ shipshift@sha256:a5e6198049fd2abc261ecb06cdbe66 e478af328ad01bb3356c4aef4698c90ba7" 10s 10s 1 {kubelet n11.humpty.ci.centos.org} spec.containers{shipshift- worker} Warning Failed Failed to pull image "172.30.254.79:5000/shipshift/ shipshift@sha256:a5e6198049fd2abc261ecb06cdbe66 e478af328ad01bb3356c4aef4698c90ba7": rpc error: code = 2 desc = manifest unknown: manifest unknown 10s 9s 2 {kubelet n11.humpty.ci.centos.org} Warning FailedSync Error syncing pod 9s 9s 1 {kubelet n11.humpty.ci.centos.org} spec.containers{shipshift- worker} Normal BackOff Back-off pulling image " 172.30.254.79:5000/shipshift/shipshift@sha256: a5e6198049fd2abc261ecb06cdbe66e478af328ad01bb3356c4aef4698c90ba7"
On Tue, Sep 26, 2017 at 9:36 AM, Scott Hebert shebert@redhat.com wrote:
I believe it is 172.30.254.79:5000
you can see this when Builds/Image Streams from the console.
-- Scott Hebert Software Engineering
On Tue, Sep 26, 2017 at 9:28 AM, Anton Sherkhonov asherkho@redhat.com wrote:
Hi,
Does anyone know the ip of the internal registry of the openshift cluster?
Thanks, Anton.
Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users