Skip to content
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.

On getting fyre env ocp 4.3 cluster the internal image registry is messed up and could not be accessed via pipelines #204

Open
aadeshpa opened this issue Apr 21, 2020 · 2 comments
Assignees

Comments

@aadeshpa
Copy link

When we use internal openshift image registry and try to run pipeline which tries to push container image to internal registry, it gives below issues

Getting image source signatures
Get http://image-registry.openshift-image-registry.svc:5000/v2/: dial tcp 172.30.237.211:5000: connect: connection refused

or

Getting image source signatures
Get http://image-registry.openshift-image-registry.svc:5000/v2/: dial tcp 172.30.129.78:5000: i/o timeout
[root@eva-inf sample-helper-files]# 

We could not use internal image registry internal url to run a pipeline and push images to it successfully

@marikaj123
Copy link
Member

Ashish, please assign it to the appropriate owne and release. Thank you.

@aadeshpa
Copy link
Author

aadeshpa commented May 1, 2020

@marikaj123
We are not sure who would take a look at this issue, @tseelbach asked me to open this in kabanero-foundation repo. We have same one created on our pipelines repo side as well as per discussion with @kvijai82 .

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants