Bug 1324727 - Docker failed to get started after downgrade
Summary: Docker failed to get started after downgrade
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Brenton Leanhardt
QA Contact: Ma xiaoqiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-07 06:22 UTC by Gaoyun Pei
Modified: 2016-07-04 00:46 UTC (History)
6 users (show)

Fixed In Version: openshift-ansible-3.0.79-1.git.0.9c75f11.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-12 16:40:15 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1065 0 normal SHIPPED_LIVE Red Hat OpenShift Enterprise atomic-openshift-utils bug fix update 2016-05-12 20:32:56 UTC

Comment 1 Brenton Leanhardt 2016-04-07 13:10:23 UTC 
Any ideas here?  I'll be on the lookout for this as I work on https://github.com/openshift/openshift-ansible/pull/1718 today.
Comment 7 Gaoyun Pei 2016-04-13 02:39:20 UTC 
Verify this with openshift-ansible-3.0.79-1.git.0.9c75f11.el7.noarch.

After docker downgraded to docker-1.8.2-10, docker could start successfully. And no errors in ansible job.

QE will move this to VERIFIED once openshift-ansible-3.0.79-1.git.0.9c75f11.el7.noarch was included in an Errata puddle.
Comment 8 Gaoyun Pei 2016-04-13 23:41:18 UTC 
Move this to verified since atomic-openshift-utils-3.0.79-1.git.0.9c75f11.el7.noarch.rpm has been shipped in AtomicOpenShift-errata/3.2/2016-04-13.2 puddle.
Comment 10 errata-xmlrpc 2016-05-12 16:40:15 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-2016:1065
Note You need to log in before you can comment on or make changes to this bug.