Bug 1271679

Summary:	instack should not install unit tests
Product:	Red Hat OpenStack	Reporter:	Mike Burns <mburns>
Component:	instack	Assignee:	Mike Burns <mburns>
Status:	CLOSED ERRATA	QA Contact:	Alexander Chuzhoy <sasha>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0 (Kilo)	CC:	dmacpher, mburns, rhel-osp-director-maint, sasha, sclewis
Target Milestone:	y2	Keywords:	Triaged
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	instack-0.0.7-2.el7ost	Doc Type:	Bug Fix
Doc Text:	Essentially the same text as BZ#1271700. Setting doc_text flag to NACK.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-12-21 16:55:47 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1271670

Description Mike Burns 2015-10-14 13:47:55 UTC

instack is currently installing unit tests and those should not be shipped.  This is with the latest OSPd 7.1 package.

Comment 4 Alexander Chuzhoy 2015-11-30 18:02:58 UTC

FailedQA:

Environment:
instack-undercloud-2.1.2-34.el7ost.noarch
instack-0.0.7-2.el7ost.noarch

The directory "/usr/lib/python2.7/site-packages/instack_undercloud/tests/" still exists.

Comment 5 Mike Burns 2015-12-03 15:46:05 UTC

instack test files were previously stored under:

/usr/lib/python2.7/site-packages/instack/tests which does not exist in the latest version of the instack package

# rpm -qlp instack-0.0.7-2.el7ost.noarch.rpm |grep test
#

Comment 6 Alexander Chuzhoy 2015-12-18 15:28:34 UTC

Verified:

Environment:
instack-0.0.7-2.el7ost.noarch


Based on comment #5, verified that /usr/lib/python2.7/site-packages/instack/tests
directory doesn't exist upon deployment.

Comment 8 errata-xmlrpc 2015-12-21 16:55:47 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://access.redhat.com/errata/RHBA-2015:2651