Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1542324 - master api and controller service cannot automatically start after host reboot while enabling system containers
master api and controller service cannot automatically start after host reboo...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
3.9.0
Unspecified Unspecified
unspecified Severity medium
: ---
: 3.9.0
Assigned To: Michael Gugino
Qin Ping
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-02-06 00:39 EST by Qin Ping
Modified: 2018-03-28 10:26 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-03-28 10:25:43 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-2018:0489 None None None 2018-03-28 10:26 EDT

  None (edit)
Description Qin Ping 2018-02-06 00:39:52 EST
Similar to bug: https://bugzilla.redhat.com/show_bug.cgi?id=1507800
Comment 1 Michael Gugino 2018-02-06 13:46:07 EST
This is caused by the docker.service unit not being enabled in favor of container-engine.service unit when using system containers.

This will need correcting in origin and openshift-ansible.

origin pr: https://github.com/openshift/origin/pull/18481

openshift-ansible pr: https://github.com/openshift/openshift-ansible/pull/7031
Comment 3 Qin Ping 2018-02-21 21:51:22 EST
Verified in openshift v3.9.0-0.47.0.
Comment 6 errata-xmlrpc 2018-03-28 10:25:43 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-2018:0489

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