Bug 1317755
Summary: | Should append openshift.node.portal_net to INSECURE_REGISTRY in docker configuration | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Ma xiaoqiang <xiama> |
Component: | Installer | Assignee: | Jason DeTiberus <jdetiber> |
Status: | CLOSED ERRATA | QA Contact: | Ma xiaoqiang <xiama> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.2.0 | CC: | aos-bugs, bleanhar, ejacobs, jokerman, mmccomas, tdawson, xtian |
Target Milestone: | --- | Keywords: | Regression, TestBlocker |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-05-12 16:38:39 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
Ma xiaoqiang
2016-03-15 06:31:47 UTC
I think there was a recent refactoring that may have changed this. https://github.com/openshift/openshift-ansible/commit/1565bc6e71bdda712d4cfdbf28754f00b38a4674#diff-a3b01e0fba2f0584a64aa9ac03ada32dL48 This appears to be where setting the portal net was removed from the docker role. This now breaks OpenShift builds because the internal registry is not used as an "insecure registry". PR to address this is here: https://github.com/openshift/openshift-ansible/pull/1614 This should be in the v3.2.0.4 build which was created today. Setting back to assigned, this hasn't been merged yet and is still being tested. Install env via openshift-ansible <--snip--> openshift_master_portal_net="172.31.0.0/16" <--snip--> check the docker configuration OPTIONS=' --selinux-enabled --insecure-registry=172.31.0.0/16 ' Get the expected result, move this issue to VERIFIED. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1065 |