Description of problem: ectd cluster install fails when differently named network interfaces are used Version-Release number of selected component (if applicable): Latest How reproducible: Customer Steps to Reproduce: Set up to install etcd clusterd on a host with interface "ens192" and another host wiht "eth02" Actual results: fatal: [uslv-dpas-etc04.amgen.com] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute u'ansible_ens192'", 'failed': True} fatal: [uslv-dpas-etc04.amgen.com] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute u'ansible_ens192'", 'failed': True} fatal: [aws-dpas-etc06.amgen.com] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute u'ansible_eth0'", 'failed': True} fatal: [aws-dpas-etc06.amgen.com] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute u'ansible_eth0'", 'failed': True} Expected results: Pass Additional info: https://github.com/openshift/openshift-ansible/blob/0ded8248eedf3ad1ceac44eac486e83a53960bb5/roles/etcd/templates/etcd.conf.j2#L4-L6
*** Bug 1267740 has been marked as a duplicate of this bug. ***
See Bug #1267740 for more detail. This should be ready for testing and it looks like Gao Yun has been working on it too. https://github.com/openshift/openshift-ansible/pull/437
Added a fix to https://github.com/openshift/openshift-ansible/pull/702 to correct the original issue of trying to reference the wrong interface on different hosts.
The same error as https://bugzilla.redhat.com/show_bug.cgi?id=1272201#c10 Move this to Assigned
I updated https://github.com/openshift/openshift-ansible/pull/702 to address some edge cases. We now test to make sure that we can read the variables we expect from the interface specified by etcd_interface for the specified host. If you are still seeing issues, please update with the inventory file you are using as well as the output of `ip addr` on the hosts.
This issue is actually a sub-issue in BZ#1272201, so will track the progress in BZ#1272201. Once BZ#1272201 is verified, this bug could be moved to verified too.
Move this bug to VERIFIED as BZ#1272201 is verified.