Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1378274 - [dev-preview-int] atomic-openshift-master-controllers crash repeatedly
[dev-preview-int] atomic-openshift-master-controllers crash repeatedly
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Pod (Show other bugs)
3.3.0
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Derek Carr
DeShuai Ma
:
Depends On: 1377483
Blocks: OSOPS_V3
  Show dependency treegraph
 
Reported: 2016-09-21 22:33 EDT by Troy Dawson
Modified: 2016-09-27 05:47 EDT (History)
17 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1377483
Environment:
Last Closed: 2016-09-27 05:47:38 EDT
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 Product Errata RHBA-2016:1933 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.3 Release Advisory 2016-09-27 09:24:36 EDT

  None (edit)
Comment 3 DeShuai Ma 2016-09-23 05:20:31 EDT
Do regression test on aws with elb HA env, no bugs found and atomic-openshift-master-controllers doesn't crash. 

verify version: atomic-openshift-3.3.0.32-1.git.0.37bd7ea.el7.x86_64
Comment 4 Bing Li 2016-09-23 06:25:46 EDT
Finished testing against online dev-preview-int v3.3.0.32. No new regression bug was found. Thanks!
Comment 6 errata-xmlrpc 2016-09-27 05:47:38 EDT
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-2016:1933

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