Bug 1628902
Summary: | Meet 'openshift_is_atomic' is undefined during execute CNS standalone deployment playbook with glusterfs_registry group | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Wenkai Shi <weshi> |
Component: | Installer | Assignee: | Jose A. Rivera <jarrpa> |
Status: | CLOSED ERRATA | QA Contact: | Qin Ping <piqin> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.11.0 | CC: | aos-bugs, jarrpa, jokerman, mgugino, mmccomas, nberry, wsun |
Target Milestone: | --- | ||
Target Release: | 3.11.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1624284 | Environment: | |
Last Closed: | 2018-11-20 03:10:43 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: | 1624284 | ||
Bug Blocks: |
Comment 3
Michael Gugino
2018-09-18 21:50:56 UTC
Also, you need to specify glusterfs_ip for each glusterfs_registry host. Referened PR is merged into release-3.11 already. Verified with: openshift-ansible-3.11.38-1.git.0.d146f83.el7.noarch TASK [openshift_node : Install GlusterFS storage plugin dependencies] **************************************************************************************** task path: /usr/share/ansible/openshift-ansible/roles/openshift_node/tasks/glusterfs.yml:2 ok: [qe-piqin-4-master-etcd-1.1104-6kt.qe.rhcloud.com] => {"attempts": 1, "changed": false, "msg": "", "rc": 0, "results": ["glusterfs-fuse-3.13.2-2.el7.x86_64 providing glusterfs-fuse is already installed"]} ok: [qe-piqin-4-node-registry-router-1.1104-6kt.qe.rhcloud.com] => {"attempts": 1, "changed": false, "msg": "", "rc": 0, "results": ["glusterfs-fuse-3.12.2-18.el7.x86_64 providing glusterfs-fuse is already installed"]} ok: [qe-piqin-4-node-1.1104-6kt.qe.rhcloud.com] => {"attempts": 1, "changed": false, "msg": "", "rc": 0, "results": ["glusterfs-fuse-3.12.2-18.el7.x86_64 providing glusterfs-fuse is already installed"]} ok: [qe-piqin-4-glusterfs-registry-node-2.1104-6kt.qe.rhcloud.com] => {"attempts": 1, "changed": false, "msg": "", "rc": 0, "results": ["glusterfs-fuse-3.12.2-18.el7.x86_64 providing glusterfs-fuse is already installed"]} ok: [qe-piqin-4-glusterfs-registry-node-1.1104-6kt.qe.rhcloud.com] => {"attempts": 1, "changed": false, "msg": "", "rc": 0, "results": ["glusterfs-fuse-3.12.2-18.el7.x86_64 providing glusterfs-fuse is already installed"]} ok: [qe-piqin-4-glusterfs-registry-node-3.1104-6kt.qe.rhcloud.com] => {"attempts": 1, "changed": false, "msg": "", "rc": 0, "results": ["glusterfs-fuse-3.12.2-18.el7.x86_64 providing glusterfs-fuse is already installed"]} 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:3537 |