Bug 1386783 - Tempest cannot load core plugins after installation of the openstack-packstack package
Summary: Tempest cannot load core plugins after installation of the openstack-packstac...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tempest
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Chandan Kumar
QA Contact: tkammer
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-19 15:45 UTC by Gabriel Szasz
Modified: 2016-10-19 17:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-19 16:06:50 UTC
Target Upstream Version:


Attachments (Terms of Use)
Output of the tools/config_tempest command. (10.00 KB, application/x-tar)
2016-10-19 15:45 UTC, Gabriel Szasz
no flags Details

Description Gabriel Szasz 2016-10-19 15:45:17 UTC
Created attachment 1212189 [details]
Output of the tools/config_tempest command.

Description of problem:
The Tempest is not able run without installing plugins 


Version-Release number of selected component (if applicable):
12.2.1-0.20161004111913.ef2befe.1.el7ost

How reproducible:


Steps to Reproduce:
1. Setup Open Stack using OSPd into virtual environment e.g. using OSPD-Customized-Deployment Jenkins job [1].
2. Log into the undercloud node.
3. Convince yourself whether openstack-tempest package is installed.
4. Convince yourself whether external public network is created in overcloud.
5. Convince yourself whether tempest-deployer-input.conf was created by OSP-d.
6. Create tempest directory and cd into the directory.
7. source ~/overcloudrc
8. Run: tools/config_tempest.py \
--deployer-input ~/tempest-deployer-input.conf \
--debug --create identity.uri $OS_AUTH_URL \
identity.admin_password $OS_PASSWORD \
--network-id <OVERCLOUD_PUBLIC_NETWORK_ID>

[1] https://rhos-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/OSPD-Customized-Deployment/build?delay=0sec

Actual results:

The command results in following critical error:

  ImportError: No module named tests.tempest.plugin

(See attachment for detailed traceback)


Expected results:

The command should configure tempest for further validating overcloud.


Additional info:
Apparently core tempest plugins are not installed.  Those should be set as dependencies of the openstack-packstack package.

Comment 1 Daniel Mellado 2016-10-19 16:06:50 UTC
Hi Gabriel, if anything this will be put into documentation but that's the intended way of running tempest now, I'll have chandan guide you through the new process.

Thanks!

Comment 2 Chandan Kumar 2016-10-19 17:24:11 UTC
Hi Gabriel,

As per the attached traceback file, It appears that python-neutron-tests (which contains tempest plugin and tempest tests for neutron) is not installed.

Currently opensack-tempest-12.2.0 onwards does not installs the component tempest plugin and component test packages. It currently install the tempest which has python-tempest as a library and it's executable.

before running tempest, we need to make sure all the required openstack-services tempest plugin and test packages are installed on the system under test because when you invoke tempest, tempest starts discovering the tests through tempest plugins entry point. Currently tempest plugin entry point has the definition from where to find the respective component test package and these entry points are installed by main package i.e openstack-component package.

Since test packages are coming from python-<component>-tests or -tempest subpackage and it is not installed, then tempest will give "ImportError: No module named tests.tempest.plugin" errors.

To fix this issue, once you install openstack-tempest then try to install the "Required" test packages based on the services installed on your system.

/usr/share/openstack-tempest-*/tools/install-test-packages.py script will automatically installs the test packages based on your environment. Then you are good to go ahead and configure the tempest tests.

If you want to install all the tempest plugin and test packages, openstack-tempest-all subpackage will solve your problem.

Thanks,

Chandan Kumar


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