Bug 1370240
Summary: | Tempest validation in OSP 9 doesn't work | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Ramon Acedo <racedoro> |
Component: | openstack-manila | Assignee: | Tom Barron <tbarron> |
Status: | CLOSED ERRATA | QA Contact: | nlevinki <nlevinki> |
Severity: | unspecified | Docs Contact: | Don Domingo <ddomingo> |
Priority: | unspecified | ||
Version: | 9.0 (Mitaka) | CC: | apevec, dmellado, dschoenb, egafford, jschluet, lhh, mapiccin, slinaber, tbarron |
Target Milestone: | async | Keywords: | ZStream |
Target Release: | 9.0 (Mitaka) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-manila-2.0.0-6.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-10-05 19:13:10 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: | |
Embargoed: |
Description
Ramon Acedo
2016-08-25 17:04:10 UTC
I dug into this a little bit this morning and discovered that this is an issue with our Tempest package not including the test_utils.py file in the tempest/lib/common/utils directory. Without that, we cannot import that class. It's also known upstream that the Manila Tempest Scenario tests are in a bad way and need some serious tending to. A possible solution would be to bring the test_utils module into our shipped version of Tempest or to update the Manila Tempest Scenario tests to not use that library. As a workaround, this worked for me: * Removed all the manila packages, including python-manilaclient, which is a dependency of openstack-tempest * Reinstalled openstack-tempest * Deleted the contents in tempest directory and recreated them with /usr/share/openstack-tempest-10.0.0/tools/configure-tempest-directory After this I can now run tempest tests from the Undercloud in OSP 9. 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://rhn.redhat.com/errata/RHBA-2016-2033.html |