Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1319922 - python-tempest-libs: 7.3->8.0 yum upgrade fails due to conflict in python-tempest-lib version.
python-tempest-libs: 7.3->8.0 yum upgrade fails due to conflict in python-te...
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tempest-lib (Show other bugs)
8.0 (Liberty)
Unspecified Unspecified
unspecified Severity unspecified
: ga
: 8.0 (Liberty)
Assigned To: RHOS Maint
Alexander Chuzhoy
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-03-21 16:18 EDT by Alexander Chuzhoy
Modified: 2016-04-07 17:35 EDT (History)
6 users (show)

See Also:
Fixed In Version: python-tempest-lib-0.13.0-3.el7ost
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-04-07 17:35:44 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 RHEA-2016:0603 normal SHIPPED_LIVE Red Hat OpenStack Platform 8 Enhancement Advisory 2016-04-07 20:53:53 EDT

  None (edit)
Description Alexander Chuzhoy 2016-03-21 16:18:34 EDT
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 11:42:54 EDT
Verified:
Environment:
python-tempest-lib-0.13.0-3.el7ost.noarch

Successfully upgraded the packages.
Comment 5 errata-xmlrpc 2016-04-07 17:35:44 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/RHEA-2016-0603.html

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