Bug 1630375
Summary: | health check failed for docker_image_availability in disconnected environment | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Sudarshan Chaudhari <suchaudh> |
Component: | Cluster Version Operator | Assignee: | Scott Dodson <sdodson> |
Status: | CLOSED DUPLICATE | QA Contact: | Johnny Liu <jialiu> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.10.0 | CC: | aos-bugs, jokerman, mkim, mmccomas, msomasun, openshift-bugs-escalate, pkanthal, rhowe, sdodson, suchaudh, syangsao |
Target Milestone: | --- | ||
Target Release: | 3.10.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-11-27 16:21:54 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sudarshan Chaudhari
2018-09-18 13:23:33 UTC
Do those images not exist at the path specified? If they exist at a different path what's that path? What's the value for oreg_url? I assume oreg_url=satellite.ocp-cluster.internal:5000/ocp-cluster-red_hat_container_catalog-ose-${component}:${version} With the issue being that the registry url is being duplicated, this commit should resolve the issue seen in this bug. https://github.com/openshift/openshift-ansible/commit/f4ad0aad0ba06e4f265c24b7ab278725b413b531#diff-f6d4c415edd5332159aa1c77eb72b757L43 With this commit skopeo command will not add {registry} to the images. All versions of openshift-ansible attached to this bug do not include the commit. This commit is available in the latest openshift-ansible rpms. Confirmed its present in these versions which are the latest at the time of writing this: openshift-ansible-3.11.43-1 openshift-ansible-3.10.73-1 Similar bug: https://bugzilla.redhat.com/show_bug.cgi?id=1613100 Per comment 25 this is fixed in the latest 3.10 and 3.11 builds. Anyone using releases previous to that should simply disable the check as a workaround. *** This bug has been marked as a duplicate of bug 1613100 *** |