Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1524460 - [3.6] Build stuck in Running Pod status shows Init:0/2
[3.6] Build stuck in Running Pod status shows Init:0/2
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Pod (Show other bugs)
3.6.0
Unspecified Unspecified
high Severity high
: ---
: 3.6.z
Assigned To: Andrew McDermott
Vikas Laad
: DeliveryBlocker, Reopened, TestBlocker
Depends On: 1486356
Blocks:
  Show dependency treegraph
 
Reported: 2017-12-11 09:54 EST by Eric Rich
Modified: 2018-01-23 12:59 EST (History)
17 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1486356
Environment:
Last Closed: 2018-01-23 12:59:00 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3307941 None None None 2018-01-03 18:00 EST
Red Hat Product Errata RHBA-2018:0113 normal SHIPPED_LIVE OpenShift Container Platform 3.7 and 3.6 bug fix and enhancement update 2018-01-23 17:55:59 EST

  None (edit)
Comment 4 Vikas Laad 2017-12-14 13:15:05 EST
Completed multiple rounds of eap concurrent builds on following version, did not see the problem.

openshift v3.6.173.0.87
kubernetes v1.6.1+5115d708d7
etcd 3.2.1
Comment 9 Vikas Laad 2017-12-16 10:51:16 EST
Fix is available in following build, verified the fix by running multiple cycle of eap concurrent builds and did not encounter the issue.

openshift v3.6.173.0.89
kubernetes v1.6.1+5115d708d7
etcd 3.2.1
Comment 16 errata-xmlrpc 2018-01-23 12:59:00 EST
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:0113

Note You need to log in before you can comment on or make changes to this bug.