Comment 2 for bug 1743688
Revision history for this message
| saswati (saswati1) wrote Re: Tempest unable to detect service availability properly, causing congress tests to fail | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
Yea, this is issue at least for congress plugin tests. let me describe from where issue started and what can be potential fix:
Congress issue:
aodh and ceilometer tempest plugins are merged into single repo now - telemetry-
Now what happened, congress tempest plugin which is user of aodh and ceilometer tempest plugin interfaces to gets both service available in service_available config group (because of default value). Even Aodh service has not been installed in congress's job setup. This is issue and causing false service availability to congress tests.
General issue:
This issue can considered as general case also where service is being installed and setup bu different repo/pckg (project) and service_available config options is being registered with default value by separate repo (tempest plugin tests).
There can be case where actual service is not installed but you install the plugin for interface usage etc. This is what happening in gate for congress case now.
As solution we can give ownership of setting the service_available options on devstack side which should check actual service availability before setting it to true/false.
Now question is whether it can be done on devstack side[1] or devstack plugin of each service. Devstack plugin can give same issue as it would not run if service is not installed.
..1 https:/