Submitter: Jenkins
Branch:    master

commit eff4f621f648c1bc84949ac52a1346844b9b6c7c
Author: Thomas Bechtold <>
Date:   Fri Aug 19 12:51:01 2016 +0200

    Fix tempest.conf generation
    [service_available] isn't being generated. This patch fixes it.
    It also introduces a switch to disable the ec2api tempest tests via
    the [service_available]ec2api parameter.
    Closes-Bug: #1613542
    Change-Id: I79e2bc26f86b3be6a45a2ee8ea33c50977d44838

** Changed in: ec2-api
       Status: In Progress => Fix Released

You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.

  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 Committed
Status in Ironic:
  In Progress
Status in Ironic Inspector:
  Fix Released
Status in OpenStack Identity (keystone):
Status in Magnum:
  Fix Released
Status in neutron:
Status in OpenStack Data Processing ("Sahara") sahara-tests:
  Fix Released
Status in senlin:
  In Progress
Status in Vitrage:
  In Progress
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 

  Steps to reproduce:

  $ tox -egenconfig
  $ source .tox/genconfig/bin/activate
  $ oslo-config-generator --config-file 
 --output-file tempest.conf.sample

  Now check the [service_available] section from tempest.conf.sample

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to