Bug 1319922 - python-tempest-libs: 7.3->8.0 yum upgrade fails due to conflict in python-tempest-lib version.
Summary: python-tempest-libs: 7.3->8.0 yum upgrade fails due to conflict in python-te...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tempest-lib
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ga
: 8.0 (Liberty)
Assignee: RHOS Maint
QA Contact: Alexander Chuzhoy
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-21 20:18 UTC by Alexander Chuzhoy
Modified: 2016-04-07 21:35 UTC (History)
6 users (show)

Fixed In Version: python-tempest-lib-0.13.0-3.el7ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-07 21:35:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:0603 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 8 Enhancement Advisory 2016-04-08 00:53:53 UTC

Description Alexander Chuzhoy 2016-03-21 20:18:34 UTC 
python-tempest-libs:  7.3->8.0 yum upgrade fails due to conflict in python-tempest-lib version.

Environment:
python-tempest-lib-0.13.0-2.el7ost.noarch

Steps to reproduce:
1. Deploy 7.3 undercloud.
2. Make sure the yum repos are updated to point to 8.0
3. Run yum update.


Result:
yum update fails.
Complaints about python-tempest-lib


Expected result:
Successful yum update.

Note:
You can remove the python-tempest-lib RPM and run yum update.
Comment 4 Alexander Chuzhoy 2016-04-04 15:42:54 UTC 
Verified:
Environment:
python-tempest-lib-0.13.0-3.el7ost.noarch

Successfully upgraded the packages.
Comment 5 errata-xmlrpc 2016-04-07 21:35:44 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://rhn.redhat.com/errata/RHEA-2016-0603.html
Note You need to log in before you can comment on or make changes to this bug.