RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1360786 - Missing python2-heatclient rpm during undercloud upgrade Liberty to Mitaka
Summary: Missing python2-heatclient rpm during undercloud upgrade Liberty to Mitaka
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: RDO
Classification: Community
Component: Package Review
Version: Mitaka
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: trunk
Assignee: hguemar
QA Contact: hguemar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-27 13:31 UTC by Adriano Petrich
Modified: 2016-07-27 22:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 22:28:10 UTC
Embargoed:


Attachments (Terms of Use)

Description Adriano Petrich 2016-07-27 13:31:49 UTC
Description of problem:
undercloud upgrade fails 

Error: Package: python2-heatclient-1.1.0-1.el7.noarch (delorean-mitaka-testing)
           Requires: python-osc-lib
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
Command '['sudo', 'yum', 'update', '-y']' returned non-zero exit status 1

Version-Release number of selected component (if applicable):


How reproducible:
Very

Steps to Reproduce:
1. Install a Liberty openstack
2. upgrade de undercloud to mitaka
3. 

Actual results:
Upgrade fails 
Full log at https://ci.centos.org/artifacts/rdo/jenkins-tripleo-quickstart-upgrade-major-liberty-to-mitaka-43/undercloud/home/stack/upgrade_undercloud.log.gz

jenkins periodic job with the failure https://ci.centos.org/view/rdo/view/tripleo-periodic/job/tripleo-quickstart-upgrade-major-liberty-to-mitaka/43/

Expected results:
Undercloud is upgraded

Additional info:

Comment 1 Adriano Petrich 2016-07-27 22:28:10 UTC
I think python2-heatclient-1.1.0-2.el7.noarch was promoted and the undercloud upgrade passed. This error is not happening anymore


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