Version-Release number of selected component (if applicable): openshift v3.10.0-0.50.0 openshift-ansible-3.10.0-0.50.0.git.0.bd68ade.el7.noarch
I hit this as well using openshift-ansible master latest (as of 24 May) and with openshift-ansible 3.10.0-0.50.0. After downgrading to openshift-ansible 3.10.0-0.47.0 the install worked. [2018-05-24 13:03:30,878][ERROR][com.floragunn.searchguard.action.configupdate.TransportConfigUpdateAction] [logging-es-data-master-3lnl2ws1] Failure while checking .searchguard.logging-es-data-master-3lnl2ws1 index MasterNotDiscoveredException[null] MasterNotDiscoveredException[null] at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$5.onTimeout(TransportMasterNodeAction.java:234) at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:236) at org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:816) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
https://github.com/openshift/openshift-ansible/pull/8522
Block testing about clustered ES related cases
Verified on openshift v3.10.0-0.60.0.
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:1816