Description of problem:

non-fatal errors are raised during installation of ha masters.

the errors result in delays during install and the appearance of failure.


Version-Release number of selected component (if applicable):

3.0.20-1.git.0.3703f1b.el7aos.noarch


How reproducible:

100%


Steps to Reproduce:
1. ha master inventory, e.g.
[masters]
192.1.0.[3:5] openshift_hostname="{{ ansible_default_ipv4.address}}" openshift_public_hostname="{{ ansible_default_ipv4.address }}" openshift_public_ip="{{ ansible_default_ipv4.address }}"

2. ansible-playbook -i inventory /usr/share/ansible/openshift-ansible/playbooks/byo/config.yml

3. there is no 3


Actual results:

TASK: [openshift_master | Start and enable master controller] *****************
failed: [192.1.0.3] => {"failed": true}
msg: Job for atomic-openshift-master-controllers.service failed because the control process exited with error code. See "systemctl status atomic-openshift-master-controllers.service" and "journalctl -xe" for details.
...ignoring

note, the restart attempt on 192.1.0.3 succeeds and i can confirm the master is running via systemctl status.

TASK: [openshift_master | Start and enable master controller] *****************
failed: [192.1.0.4] => {"failed": true}
msg: Job for atomic-openshift-master-controllers.service failed because the control process exited with error code. See "systemctl status atomic-openshift-master-controllers.service" and "journalctl -xe" for details.
...ignoring

NOTIFIED: [openshift_master | restart master controllers] *********************
failed: [192.1.0.4] => {"failed": true}
msg: Job for atomic-openshift-master-controllers.service failed because the control process exited with error code. See "systemctl status atomic-openshift-master-controllers.service" and "journalctl -xe" for details.
...ignoring

TASK: [openshift_master | Start and enable master controller] *****************
failed: [192.1.0.5] => {"failed": true}
msg: Job for atomic-openshift-master-controllers.service failed because the control process exited with error code. See "systemctl status atomic-openshift-master-controllers.service" and "journalctl -xe" for details.
...ignoring

NOTIFIED: [openshift_master | restart master controllers] *********************
failed: [192.1.0.5] => {"failed": true}
msg: Job for atomic-openshift-master-controllers.service failed because the control process exited with error code. See "systemctl status atomic-openshift-master-controllers.service" and "journalctl -xe" for details.
...ignoring



Expected results:

no errors


Additional info:

the master controllers are in fact running, they're just waiting on a lease -

ssh 192.1.0.4 systemctl status atomic-openshift-master-controllers.service
● atomic-openshift-master-controllers.service - Atomic OpenShift Master Controllers
   Loaded: loaded (/usr/lib/systemd/system/atomic-openshift-master-controllers.service; enabled; vendor preset: disabled)
   Active: activating (start) since Sun 2016-01-03 22:40:31 EST; 13s ago
     Docs: https://github.com/openshift/origin
 Main PID: 21016 (openshift)
   CGroup: /system.slice/atomic-openshift-master-controllers.service
           └─21016 /usr/bin/openshift start master controllers --config=/etc/origin/master/master-config.yaml --loglevel=2 --listen=https://0.0.0.0:8444
Jan 03 22:40:31 192.1.0.4 systemd[1]: Starting Atomic OpenShift Master Controllers...
Jan 03 22:40:32 192.1.0.4 atomic-openshift-master-controllers[21016]: I0103 22:40:32.525344   21016 plugins.go:71] No cloud provider specified.
Jan 03 22:40:32 192.1.0.4 atomic-openshift-master-controllers[21016]: I0103 22:40:32.682340   21016 start_master.go:410] Starting controllers on 0.0.0.0:8444 (v3.1.0.4-16-g112fcc4)
Jan 03 22:40:32 192.1.0.4 atomic-openshift-master-controllers[21016]: I0103 22:40:32.682995   21016 start_master.go:414] Using images from "openshift3/ose-<component>:v3.1.0.4"
Jan 03 22:40:32 192.1.0.4 atomic-openshift-master-controllers[21016]: I0103 22:40:32.683346   21016 master.go:232] Started health checks at 0.0.0.0:8444
Jan 03 22:40:32 192.1.0.4 atomic-openshift-master-controllers[21016]: I0103 22:40:32.683770   21016 master_config.go:250] Attempting to acquire controller lease as master-t3uwlee7, renewing every 30 seconds

ssh 192.1.0.5 systemctl status atomic-openshift-master-controllers.service
● atomic-openshift-master-controllers.service - Atomic OpenShift Master Controllers
   Loaded: loaded (/usr/lib/systemd/system/atomic-openshift-master-controllers.service; enabled; vendor preset: disabled)
   Active: activating (start) since Sun 2016-01-03 22:44:22 EST; 36s ago
     Docs: https://github.com/openshift/origin
 Main PID: 21032 (openshift)
   CGroup: /system.slice/atomic-openshift-master-controllers.service
           └─21032 /usr/bin/openshift start master controllers --config=/etc/origin/master/master-config.yaml --loglevel=2 --listen=https://0.0.0.0:8444
Jan 03 22:44:22 192.1.0.5 systemd[1]: Starting Atomic OpenShift Master Controllers...
Jan 03 22:44:24 192.1.0.5 atomic-openshift-master-controllers[21032]: I0103 22:44:24.432969   21032 plugins.go:71] No cloud provider specified.
Jan 03 22:44:24 192.1.0.5 atomic-openshift-master-controllers[21032]: I0103 22:44:24.792731   21032 start_master.go:410] Starting controllers on 0.0.0.0:8444 (v3.1.0.4-16-g112fcc4)
Jan 03 22:44:24 192.1.0.5 atomic-openshift-master-controllers[21032]: I0103 22:44:24.792809   21032 start_master.go:414] Using images from "openshift3/ose-<component>:v3.1.0.4"
Jan 03 22:44:24 192.1.0.5 atomic-openshift-master-controllers[21032]: I0103 22:44:24.793514   21032 master.go:232] Started health checks at 0.0.0.0:8444
Jan 03 22:44:24 192.1.0.5 atomic-openshift-master-controllers[21032]: I0103 22:44:24.794837   21032 master_config.go:250] Attempting to acquire controller lease as master-256rr3ye, renewing every 30 seconds


this may be related to https://github.com/ansible/ansible-modules-core/issues/2265