Red Hat Bugzilla – Bug 1357984
Wrong error message when using openshift ansible playbook
Last modified: 2017-12-18 22:22:07 EST
Description of problem: Trying to install Openshift 3.3 cluster anible playbook run is failing with a wrong error message. TASK [openshift_facts : Verify Ansible version is greater than or equal to 2.1.0.0] *** Tuesday 19 July 2016 15:54:44 +0000 (0:00:01.005) 1:11:24.007 ********** fatal: [ec2-54-187-247-212.us-west-2.compute.amazonaws.com]: FAILED! => {"failed": true, "msg": "The conditional check 'persistent_volumes | length > 0 or persistent_volume_claims | length > 0' failed. The error was: u'{{ hostvars[groups.oo_first_master.0] | oo_persistent_volumes(groups) }}: oo_nfs_to_config'"} Version-Release number of selected component (if applicable): Openshift 3.3 How reproducible: When there is no storage host detected. Steps to Reproduce: 1. Create an inventory without any nfs host or nfs host group 2. Playbook fails with above error Actual results: Verify Ansible version is greater than or equal to 2.1.0.0 Expected results: failed no storage host detected Additional info:
This has been merged and is in openshift-ansible-3.3.5-1.git.0.af6025b.el7 or newer.
Verify this bug with openshift-ansible-3.3.6-1.git.0.5c681f6.el7.noarch.rpm Set openshift_hosted_registry_storage_kind=nfs in the inventory, bu no openshift_hosted_registry_storage_host and [nfs] group host specified. Run the playbook, ansible would fail and prompt no storage host detected. PLAY [Create persistent volumes] *********************************************** TASK [setup] ******************************************************************* ok: [openshift-x.com] TASK [openshift_facts : Detecting Operating System] **************************** fatal: [openshift-x.com]: FAILED! => {"failed": true, "msg": "The conditional check 'persistent_volumes | length > 0 or persistent_volume_claims | length > 0' failed. The error was: {{ hostvars[groups.oo_first_master.0] | oo_persistent_volumes(groups) }}: |failed no storage host detected"}
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:1933