Bug 1386849

Summary:	[Docs][Manual Installation][Director] Emphasize that Tempest does not work without plug-ins installed
Product:	Red Hat OpenStack	Reporter:	Gabriel Szasz <gszasz>
Component:	documentation	Assignee:	Lukas Ruzicka <lruzicka>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Kovar <pkovar>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	10.0 (Newton)	CC:	chkumar, cylopez, lbopf, mburns, srevivo
Target Milestone:	async
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-09 09:16:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Gabriel Szasz 2016-10-19 17:22:34 UTC

Description of problem:

Tempest installed via "yum install openstack-tempest" does not contain ANY plugins by default, not even plugins containing core component tests.  It means that user cannot even run tools/config_tempest.py on his/her tempest directory without additional installation of at least single plugin.  Since this Tempest behaviour is counter-intuitive, it should be reflected in the documentation.

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


How reproducible:
100%

Steps to Reproduce:
1. Install tempest using "yum install openstack-tempest".
2. Create and configure tempest directory.
3. Run run tools/config_tempest.py script to configure tempest against overcloud setup.


Actual results:

The script will fail because no tempest plugins are installed.  Documentation provides no explanation.


Expected results:

Documentation should explicitly state that user has to use either 
"yum install opensttack-tempest-all" command--that will install tempest + all plugins, or install selected plugins manually.  Documentation should also provide clear instructions how to install tempest plugins [1].

[1] https://www.rdoproject.org/blog/2016/09/running-tempest-on-rdo-openstack-newton/


Additional info:
Adding required subset of plugins manually is really an intended way of running tempest now.  See bug#1386783 for further reference.

Comment 1 Lucy Bopf 2016-12-21 07:59:48 UTC

Assigning to Lukas for review.

Lukas, this change potentially affects the Director Installation and Usage guide and the Manual Installation Procedures guide, which both cover tempest installation.

Comment 2 Lukas Ruzicka 2016-12-22 10:49:01 UTC

I updated the procedure to inform about the necessity to install the tempest plugins manually. The bug indeed involved both guides.

Comment 3 Chandan Kumar 2016-12-23 09:51:45 UTC

Hello LUkas,

Anyone can install the required tempest plugin package automatically based on the services configured by running following command:
#/usr/share/openstack-tempest-*/tools/install_test_packages.py

The openstack-tempest-all will install all the openstack services tempest plugin which might not be required on the system under test. It is better to use the above script for the same.

Thanks,

Chandan Kumar

Comment 4 Lukas Ruzicka 2016-12-23 10:57:33 UTC

(In reply to Chandan Kumar from comment #3)
> Hello LUkas,
> 
> Anyone can install the required tempest plugin package automatically based
> on the services configured by running following command:
> #/usr/share/openstack-tempest-*/tools/install_test_packages.py
> 
> The openstack-tempest-all will install all the openstack services tempest
> plugin which might not be required on the system under test. It is better to
> use the above script for the same.
> 
> Thanks,
> 
> Chandan Kumar

Thanks Chandan,

I will add your proposal to the documentation. I skipped the 

# yum install openstack-tempest-all

because I agree that in most cases this would be an overkill and in the original bug description is written, that manual installation of the packages should be advertised.

Comment 5 Petr Kovar 2017-01-03 10:56:05 UTC

*** Bug 1401966 has been marked as a duplicate of this bug. ***

Comment 6 Lukas Ruzicka 2017-01-09 09:16:11 UTC

The updated guides were uploaded to the Portal.