Description of problem: The openshift 3.9 installation with gluster is always failing with the below task. gluster installation used this playbook [#ansible-playbook -i <inventory> /usr/share/ansible/openshift-ansible/playbooks/openshift-glusterfs/config.yml -vvv] he Openshift ansible installer breaks with the following error: 1. Hosts: xxx.xxx.xxx.com Play: Configure GlusterFS Task: Generate heketi user key Message: The conditional check 'glusterfs_heketi_user_key != glusterfs_heketi_admin_key' failed. The error was: error while evaluating conditional (glusterfs_heketi_user_key != glusterfs_heketi_admin_key): 'glusterfs_heketi_user_key' is undefined This issue seems more similar to the below upstream issue. https://github.com/openshift/openshift-ansible/issues/8193 Version-Release number of the following components: $ rpm -qa | grep ansible ansible-2.5.1-1.el7.noarch $oc version openshift v3.9.33 Actual results: ansible installer failed Expected results: It should get run successfully
First, please use ansible 2.4 as documented here https://docs.openshift.com/container-platform/3.9/install_config/install/host_preparation.html#host-registration A workaround would be to set an inventory value for glusterfs_heketi_user_key which is intended to be an autogenerated random string up to 32 characters in length. https://github.com/openshift/openshift-ansible/pull/9306 is the proposed fix
@asambast, As we talked, you have no privilege to view the errata. You need to verify this bug using atomic-openshift-3.9.40-1?
Hi, I'm deploying the set up and working on this bug at priority. Meanwhile, mmariyan , Can you please attach the inventory file you used to deploy when you hit the bug? It's always better to attach the inventory file along with the logs.
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:2335