Description of problem: Deploy CNS with glusterfs_registry group configure as registry storage failed due to attribute missing. Installer failed in TASK [openshift_hosted : Mount registry volume]. Version-Release number of the following components: openshift-ansible-3.9.0-0.38.0.git.0.57e1184.el7 How reproducible: 100% Steps to Reproduce: 1. Deploy CNS with glusterfs_registry group configure as registry storage # cat hosts [OSEv3:children] masters nodes glusterfs_registry [OSEv3:vars] ... openshift_hosted_registry_storage_kind=glusterfs ... [nodes] ... glusterfs1.example.com glusterfs2.example.com glusterfs3.example.com [glusterfs_registry] glusterfs1.example.com glusterfs_devices="['/dev/sdb']" glusterfs2.example.com glusterfs_devices="['/dev/sdb']" glusterfs3.example.com glusterfs_devices="['/dev/sdb']" 2. 3. Actual results: # ansible-playbook -i hosts -v /usr/share/ansible/openshift-ansible/playbooks/deploy_cluster.yml ... TASK [openshift_hosted : Mount registry volume] ******************************** Tuesday 06 February 2018 09:48:33 +0000 (0:00:00.420) 0:36:10.525 ****** fatal: [ec2-xx-xx-xx-xx.compute-1.amazonaws.com]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'hosted'\n\nThe error appears to have been in '/usr/share/ansible/openshift-ansible/roles/openshift_hosted/tasks/storage/glusterfs.yml': line 34, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Mount registry volume\n ^ here\n\nexception type: <class 'ansible.errors.AnsibleUndefinedVariable'>\nexception: 'dict object' has no attribute 'hosted'"} ... Expected results: Installer should success. Additional info:
Which version of ansible was used in this test? This seems like a regression.
I swear we already fixed this... Scott, has something changed for 3.9 that would make a reference to "openshift.hosted.registry.storage.glusterfs.path" no longer valid?
Sorry for miss ansible version: ansible-2.4.3.0-1.el7ae Can reproduce it with this version too: ansible-2.4.2.0-2.el7
This is a regression caused by: https://github.com/openshift/openshift-ansible/pull/6969 PR Created: https://github.com/openshift/openshift-ansible/pull/7244
PR Merged.
Verified with version openshift-ansible-3.9.1-1.git.0.9862628.el7, the registry volume could mount succeed.
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:0489