Bug 1699015

Summary:	Elasticsearch-operator can get stuck on Pods in 'Pending' phase
Product:	OpenShift Container Platform	Reporter:	Josef Karasek <jkarasek>
Component:	Logging	Assignee:	Josef Karasek <jkarasek>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	aos-bugs, jcantril, qitang, rmeggins
Target Milestone:	---
Target Release:	4.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-04 10:47:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Josef Karasek 2019-04-11 14:38:03 UTC

Description of problem:
When the operand gets into 'Pending' phase, the operator cannot progress further.


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


How reproducible:
Always

Steps to Reproduce:
1. Deploy EO and some CR
2. Request more resources that the cluster has (e.g. CPU)
3. ES pod gets marked as Unschedulable and its phase is 'Pendig'
4. Correct the CR
5. The operator cannot perform corrective action, the pod is stuck in 'Pending' phase

Actual results:
Pods get stuck


Expected results:
Pods get deployed successfully

Additional info:

Comment 2 Qiaoling Tang 2019-05-05 01:52:55 UTC

Verified on quay.io/openshift/origin-elasticsearch-operator@sha256:d1f9375315fe5544e2e5e748e64a11f4d0983a36fd1bed3f74072772ea65f05b

Comment 4 errata-xmlrpc 2019-06-04 10:47:22 UTC

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-2019:0758