Bug 1332592 – Incomplete requirement on docker-common

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1332592 - Incomplete requirement on docker-common

Summary:	Incomplete requirement on docker-common

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	docker (Show other bugs)
Sub Component:
Version:	7.2
Hardware:	Unspecified Unspecified

Priority	unspecified Severity low
Target Milestone:	rc
Target Release:	---
Assigned To:	Lokesh Mandvekar
QA Contact:	atomic-bugs@redhat.com
Docs Contact:

URL:
Whiteboard:
Keywords:	Extras

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-05-03 10:28 EDT by Ed Santiago
Modified:	2016-05-12 11:18 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:	docker-1.9.1-40.el7
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-05-12 11:18:45 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)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2016:1034	normal	SHIPPED_LIVE	Moderate: docker security, bug fix, and enhancement update	2016-05-12 15:15:01 EDT

Groups: None (edit)

Description Ed Santiago 2016-05-03 10:28:49 EDT

'yum update docker' does not update docker-common, leaving mixed state on system.

Seems like an easy specfile fix (line 96):

    - Requires: %{name}-common
    + Requires: %{name}-common = %{version}-%{release}

Comment 1 Daniel Walsh 2016-05-03 11:13:39 EDT

Lokesh we need this fixed in todays builds.

Comment 3 Ed Santiago 2016-05-03 16:44:25 EDT

Tested; looks good. Thanks.

Comment 4 Luwen Su 2016-05-04 02:07:16 EDT

Per comment#3, move to verified

Comment 6 errata-xmlrpc 2016-05-12 11:18:45 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://rhn.redhat.com/errata/RHSA-2016-1034.html

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