yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #90983
[Bug 1613542] Re: tempest.conf doesn't contain $project in [service_available] section
Just like keystone, the network service is always set to True in tempest
(tempest/common/utils/__init__.py), so I'll mark this invalid for
neutron. Please create a new bug if/when this ever needs to change in
tempest and we can make an appropriate change in neutron.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1613542
Title:
tempest.conf doesn't contain $project in [service_available] section
Status in Aodh:
Fix Released
Status in Ceilometer:
Fix Released
Status in ec2-api:
Fix Released
Status in Gnocchi:
Fix Released
Status in Ironic:
Fix Released
Status in Ironic Inspector:
Fix Released
Status in OpenStack Identity (keystone):
Invalid
Status in Magnum:
Fix Released
Status in neutron:
Invalid
Status in OpenStack Data Processing ("Sahara") sahara-tests:
Fix Released
Status in senlin:
Invalid
Status in vmware-nsx:
Fix Released
Bug description:
When generating the tempest conf, the tempest plugins need to register the config options.
But for the [service_available] section, ceilometer (and the other mentioned projects) doesn't register any value so it's missng in the tempest sample config.
Steps to reproduce:
$ tox -egenconfig
$ source .tox/genconfig/bin/activate
$ oslo-config-generator --config-file .tox/genconfig/lib/python2.7/site-packages/tempest/cmd/config-generator.tempest.conf --output-file tempest.conf.sample
Now check the [service_available] section from tempest.conf.sample
To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1613542/+subscriptions