Bug 1558183

Summary:	[starter-ca-central-1] builds in pending state indefinitely
Product:	OpenShift Container Platform	Reporter:	Justin Pierce <jupierce>
Component:	Node	Assignee:	Seth Jennings <sjenning>
Status:	CLOSED CURRENTRELEASE	QA Contact:	DeShuai Ma <dma>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.9.0	CC:	aos-bugs, filbranden, jiajliu, jokerman, mmccomas, pportant, smunilla, xtian
Target Milestone:	---
Target Release:	3.9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openshift-ansible-3.9.13-1.git.0.47b616a.el7	Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-18 18:17:31 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 Justin Pierce 2018-03-19 19:03:05 UTC

Description of problem:
Builds in this cluster are spending excessive amounts of time in the Pending state.

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

Comment 7 N. Harrison Ripps 2018-03-21 14:22:28 UTC

Merged 3.9 PR.

Comment 9 liujia 2018-03-22 09:01:07 UTC

Due to revert pr related with bz1548358. Do some regression test based latest build openshift-ansible-3.9.13-1.git.0.47b616a.el7.noarch.

1) Run upgrade against non-ha deployed containerized ocp on rhel. 
upgrade succeed.
2) Run upgrade against ha deployed coordinated ocp on rhel.
upgrade succeed.

Please help confirm if that's enough for the regression test about revert pr.

Comment 10 DeShuai Ma 2018-03-22 10:05:10 UTC

DevExp:
We have triggered more than 50 builds in parallel and make sure all pods are assigned to one node, didn't meet the issue like the bug said. All builds works well and pods are running well.

Comment 11 DeShuai Ma 2018-03-22 10:06:51 UTC

QE also do regression testing for the fix. No issue now. make the bug verified.
For online starter-ca-central-1 we'd better clone a bug then after online upgrade to 3.9.13 verify it.