Bug 1613475

Tempest is branchless, so a new build should fix it.

I want this fix, too. Since RH7-RHOS-13.0 2018-07-30.2, we are hitting a Tempest failure, which is likely BZ#1609361.

Since the fix on OSP14 from BZ#1609361 is working fine, do you know how long the backport upstream to RDO/queens and then in OSP13 will take ?

python2-heat-tests-tempest-0.1.1-0.20180514163843.9d99219.el7ost is released in public without the fix, as a part of OSP13 errata RHBA-2018:2573.
python-gabi is still 1.33.

Now people will hit a failure like this if heat is enabled for tempest:

+ tempest run --concurrency 4 -s
+ tee run-tempest.log

=========================
Failures during discovery
=========================
--- import errors ---
Failed to call load_tests:
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/unittest2/loader.py", line 136, in loadTestsFromModule
    return load_tests(self, tests, pattern)
  File "/usr/lib/python2.7/site-packages/heat_tempest_plugin/tests/api/test_heat_api.py", line 96, in load_tests
    test_loader_name=__name__)
  File "/usr/lib/python2.7/site-packages/gabbi/driver.py", line 76, in build_tests
    raise AssertionError('must specify exactly one of host or intercept')
AssertionError: must specify exactly one of host or intercept

================================================================================
The above traceback was encountered during test discovery which imports all the found test modules in the specified test_path.

I have deployed testbed with RHOSP13 + NSXT2.3.0 for plugin certification:
While running testsuite, tescases are not getting loaded. 

All below RPMs are present in system:
openstack-tempest
sos
python2-neutron-tests-tempest
python2-cinder-tests-tempest
python2-manila-tests-tempest
python2-sahara-tests-tempest
python2-tempestconf
python-neutron-lbaas-tests
rhosp-release
 
Getting failure while listing tests:
 
[root@overcloud-controller-0 new]# ostestr --list
 
=========================
Failures during discovery
=========================
--- import errors ---
Failed to call load_tests:
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/unittest2/loader.py", line 136, in loadTestsFromModule
    return load_tests(self, tests, pattern)
  File "/usr/lib/python2.7/site-packages/heat_tempest_plugin/tests/api/test_heat_api.py", line 96, in load_tests
    test_loader_name=__name__)
  File "/usr/lib/python2.7/site-packages/gabbi/driver.py", line 76, in build_tests
    raise AssertionError('must specify exactly one of host or intercept')
AssertionError: must specify exactly one of host or intercept


Gabbi version on system:
[root@overcloud-controller-0 new]# rpm -qa | grep gabbi
python-gabbi-1.33.0-1.el7ost.noarch
 
Tried to upgrade gabbi version to 1.42 but could not find right way to upgrade this package:
 
[root@overcloud-controller-0 new]# yum update python-gabbi
Loaded plugins: product-id, search-disabled-repos, subscription-manager
No packages marked for update

Unable to update Gabbi version on system. Could you please help resolution of this issue.

Need to run testsuite for certification purpose.

Hi,

Try removing the heat tempest rpm called (python2-heat-tests-tempest).
#yum remove python2-heat-tests-tempest

And then try running

#ostestr --list

This should do the trick for you and unblock the cert run as heat tempest tests are not required.

Thanks,
Anshul

verified 
 [root@undercloud-0 ~]# rpm -qa | grep gabbi
python2-gabbi-1.42.1-2.el7ost.noarch

Hello Rabi,

The fix in the upstream is insufficient and it causes all tests in heat-tempest-plugin is skipped.

Current fix makes the heat-test-tempest unusable.
I filed a bugzilla for he issue as https://bugzilla.redhat.com/show_bug.cgi?id=1644957.

Could you consider to make the new bugzilla as blocker of this bugzilla?

Best Regards,
Keigo Noha

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-2018:3611