Bug 1581622
Summary: | [CNS][3.10] Installation failed due to GlusterFS pods try to pull image from docker.io | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Wenkai Shi <weshi> | |
Component: | Installer | Assignee: | Jose A. Rivera <jarrpa> | |
Status: | CLOSED ERRATA | QA Contact: | Wenkai Shi <weshi> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 3.10.0 | CC: | aos-bugs, bkunal, bleanhar, jarrpa, jokerman, mmccomas, nberry, sdodson, sjenning, tatanaka, weshi | |
Target Milestone: | --- | |||
Target Release: | 3.10.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | No Doc Update | ||
Doc Text: |
undefined
|
Story Points: | --- | |
Clone Of: | ||||
: | 1583148 (view as bug list) | Environment: | ||
Last Closed: | 2018-07-30 19:16:18 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: | ||||
Bug Depends On: | 1583500 | |||
Bug Blocks: | 1583148 |
Description
Wenkai Shi
2018-05-23 09:00:47 UTC
We haven't changed anything about this from 0.47 to 0.50. Did something change with regard to how the default registry is configured? Wenkai, Any chance that openshift_storage_glusterfs_image was set in your previous run but not these? I agree that there haven't been any changes to this code in quite some time. (In reply to Scott Dodson from comment #4) > Wenkai, > > Any chance that openshift_storage_glusterfs_image was set in your previous > run but not these? I agree that there haven't been any changes to this code > in quite some time. Hi Scott, I didn't set openshift_storage_glusterfs_image in any of this bug's installation. AS I mentioned, it may related to atomic-openshift rather than openshift-ansible, I've try deploy atomic-openshift-3.10.0-0.47.0.git.0.2fffa04.el7 with openshift-ansible-3.10.0-0.50.0.git.0.bd68ade.el7, It's doesn't appear. This issue does appear in atomic-openshift-3.10.0-0.50.0.git.0.db6dfd6.el7 so far. Give a shoot with version atomic-openshift-3.10.0-0.51.0.git.0.8bcf033.el7, still appear. Jose, have you been able to reproduce this bug by any chance? It would be very helpful to try Wenkai's reproducer and confirm it did indeed actually start happening after 3.10.0-0.47.0. I have not been able to reproduce this, I don't have a reproducible downstream environment to test on. Moving this back to modified pending further results from Wenkai. I'll try to get a downstream environment running somewhere. It could be work around by set following parameters: openshift_storage_glusterfs_heketi_image=registry.access.redhat.com/rhgs3/rhgs-volmanager-rhel7 openshift_storage_glusterfs_image=registry.access.redhat.com/rhgs3/rhgs-server-rhel7 openshift_storage_glusterfs_block_image=registry.access.redhat.com/rhgs3/rhgs-gluster-block-prov-rhel7 openshift_storage_glusterfs_s3_image=registry.access.redhat.com/rhgs3/rhgs-gluster-s3-server-rhel7 It's related: https://github.com/openshift/openshift-ansible/pull/8585 Seth, is this releated to https://bugzilla.redhat.com/show_bug.cgi?id=1583500 ? Wenkai, This problem should no longer exist in openshift-ansible-3.10.0-0.57.0 as long as oreg_url is set, have you tested this version? Neha, Brenton, Yes, but by default the installer will set fully qualified names, the inventory you're using bypasses this. I'd suggest setting fully qualified names for these variables you're setting : openshift_storage_glusterfs_heketi_image='brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rhgs3/rhgs-volmanager-rhel7' openshift_storage_glusterfs_block_image='brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rhgs3/rhgs-gluster-block-prov-rhel7' openshift_storage_glusterfs_image='brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rhgs3/rhgs-server-rhel7' Relying on the additional registries functionality is something we should put a stop to in 3.10 at least in installer code. For origin it may be wise to preserve existing behavior while making it clear that it's deprecated. (In reply to Scott Dodson from comment #16) > Wenkai, > > This problem should no longer exist in openshift-ansible-3.10.0-0.57.0 as > long as oreg_url is set, have you tested this version? > Yes, I've tested this version. I can verify it once move to ON_QA. Moving ON_QA Verified with version openshift-ansible-3.10.0-0.64.0.git.20.48df973.el7, it's can pull docker image from registry defined in oreg_url. The customer is facing the similar issue when installing CNS with OpenShift 3.9. Could you tell me setting the following parameters can be worked around?
openshift_storage_glusterfs_heketi_image=registry.access.redhat.com/rhgs3/rhgs-volmanager-rhel7
openshift_storage_glusterfs_image=registry.access.redhat.com/rhgs3/rhgs-server-rhel7
openshift_storage_glusterfs_block_image=registry.access.redhat.com/rhgs3/rhgs-gluster-block-prov-rhel7
openshift_storage_glusterfs_s3_image=registry.access.redhat.com/rhgs3/rhgs-gluster-s3-server-rhel7
After setting these parameteres, the customer now faces the following error.
> exception: 'glusterfs_heketi_url' is undefined
Takayoshi, The problems in 3.9 are not the same as what's being discussed in this bug or at least do not have the same fix as they will on 3.10. Can you please open a new bug with as much log output as possible and the inventory file you're using when you encounter the error on 3.9? Those configuration variables should be fine. Scott, Thank you for the reply. We'll check the case again and create a new BZ if needed. (In reply to Takayoshi Tanaka from comment #21) > The customer is facing the similar issue when installing CNS with OpenShift > 3.9. Could you tell me setting the following parameters can be worked around? > > openshift_storage_glusterfs_heketi_image=registry.access.redhat.com/rhgs3/ > rhgs-volmanager-rhel7 > openshift_storage_glusterfs_image=registry.access.redhat.com/rhgs3/rhgs- > server-rhel7 > openshift_storage_glusterfs_block_image=registry.access.redhat.com/rhgs3/ > rhgs-gluster-block-prov-rhel7 > openshift_storage_glusterfs_s3_image=registry.access.redhat.com/rhgs3/rhgs- > gluster-s3-server-rhel7 > > After setting these parameteres, the customer now faces the following error. > > exception: 'glusterfs_heketi_url' is undefined We have BZ #1583148 to track this issue in 3.9. For error "'glusterfs_heketi_url' is undefined", looks like another issue. 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-2018:1816 |