Bug 1395601 - openstack_verify fails to run because of conflicting packages on SUT
Summary: openstack_verify fails to run because of conflicting packages on SUT
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat OpenStack Certification Program
Classification: Retired
Component: rhoscts
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Neeti Dahiya
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-16 09:42 UTC by Alexandru Dan
Modified: 2020-03-27 15:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 15:51:56 UTC


Attachments (Terms of Use)

Description Alexandru Dan 2016-11-16 09:42:20 UTC
Description of problem:
When trying to install SUT packages on controller node the setup of the test fails because of conflicting packages shown in the logs:
Transaction check error:
  file /usr/bin/subunit-trace from install of python-os-testr-0.6.0-1.el7ost.noarch conflicts with file from package python-tempest-lib-0.0.2-3.el7.noarch

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

How reproducible:
Every time

Steps to Reproduce:
1. Install OSP9 as in the documentation
2. Fallow the certification workflow to create a test vm
3. Add the controller node as SUT in the certification suite.
4. Run openstack_verify test on the SUT

Actual results:
openstack_verify fails with conflicting packages error:
Transaction check error:
  file /usr/bin/subunit-trace from install of python-os-testr-0.6.0-1.el7ost.noarch conflicts with file from package python-tempest-lib-0.0.2-3.el7.noarch

Expected results:
Scenario should install necessary packages and run the tempest run.

Additional info:

Comment 2 Paul Pindell 2017-02-23 21:06:39 UTC
I ran into this issue as well. 

On the controller I added this repo 
   subscription-manager repos --enable=rhel-7-server-openstack-9-rpms

then 

yum install python-tempest-lib
yum -t install openstack-tempest

then re-ran the tests and got past this issue.


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