Elasticsearch becomes unavailable after upgrading to Red Hat OpenShift Container Platform to 3.9

Issue

• After upgrading OCP to version 3.9.x, the Elasticsearch pods do not change to a "Ready" state and thus Elasticsearch becomes unavailable. The KCS solution article Deploying multiple Elasticsearch pods results in MasterNotDiscoveredException did not help to resolve this issue.

• Elasticsearch pods yield the following error message:

      [2019-05-14 18:30:24,060][ERROR][com.floragunn.searchguard.action.configupdate.TransportConfigUpdateAction] [logging-es-data-master-7ti5fmmw] Failure while checking .searchguard.logging-es-data-master-7ti5fmmw 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)