verify-config KeyError with tempest plugins
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Fix Released
|
Undecided
|
Martin Kopec |
Bug Description
Let's say I install several tempest plugins, for example:
$ tempest list-plugins
+------
| Name | EntryPoint |
+------
| heat | heat_tempest_
| telemetry_tests | telemetry_
| cinder_tests | cinder_
| designate | designate_
| horizon | tempest_
| ironic_tests | ironic_
+------
Then I generate tempest.conf (manually or by python-tempestconf, doesn't really matter) and I want to verify tempest.conf by `tempest verify-config`:
$ tempest verify-config -o new_tempest.conf
Running config verification...
Traceback (most recent call last):
File "/usr/lib/
main(
File "/usr/lib/
services = check_service_
File "/usr/lib/
codename_
KeyError: 'heat_plugin'
and the same with :baremetal_
It seems verify-config doesn't count with a situation, when there is a plugin available in the system belonging to a different service than these [1], because it fails here [2].
Either we can put all known plugins to that list [1], which I believe is unrealistic and also it doesn't count with situations when a user has his own custom plugin, or verify-config should be able to create/detect such a list dynamically.
Meanwhile we should at least make verify-config not fail and inform a user that there is a situation where verify-config can't verify such plugin, f.e.: "verify config can't verify heat_plugin, baremetal_
[1] https:/
[2] https:/
Changed in tempest: | |
assignee: | nobody → Martin Kopec (mkopec) |
status: | New → In Progress |
summary: |
- verify-config and tempest plugins + verify-config KeyError with tempest plugins |
Related fix proposed to branch: master /review. openstack. org/631801
Review: https:/