Bug 1520925 – Add python-isodate to comps file for release

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

Bug 1520925 - Add python-isodate to comps file for release

Summary:	Add python-isodate to comps file for release

Status:	CLOSED ERRATA

Aliases:	None

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

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Lubos Kocman
QA Contact:	Release Test Team
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1542969
Blocks:	1511223
	Show dependency tree / graph

Reported:	2017-12-05 08:16 EST by Eng Ops Maitai User
Modified:	2018-04-10 06:22 EDT (History)
CC List:	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-04-10 06:21:41 EDT
Type:	---
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	RHEA-2018:0700	None	None	None	2018-04-10 06:22 EDT

Groups: None (edit)

Comment 2 Lubos Kocman 2017-12-05 08:32:13 EST

No change needed we just need to wait until  python-azure-sdk and python-msrest are in errata so they will get pulled into compose

Comment 8 Lubos Kocman 2018-02-07 11:39:55 EST

Moving to ON_QA as following change together with Bug 1542969 in modified should make proper placement to HA/RS only.

http://git.app.eng.bos.redhat.com/git/comps.git/commit/?id=648b2f6db5c62b9ef99ce104ad0a045a32422aa9

Change should be visible in Snap-3+

Comment 12 errata-xmlrpc 2018-04-10 06:21:41 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/RHEA-2018:0700

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