Cinder Third party driver tempest test fail after this commit https://github.com/openstack-dev/devstack/commit/b719b55b1d8158a926eb3cd0d04a2749f608a6d8

[ITRI DISCO CI]

Our OpenStack third party CI keep failing after this change.
https://github.com/openstack-dev/devstack/commit/b719b55b1d8158a926eb3cd0d04a2749f608a6d8

our pre_test_hook will write local.conf
-------------------------------------------------------
cat <<EOF >$BASE/new/devstack/local.conf

LIBS_FROM_GIT=os-brick

[[post-config|\$CINDER_CONF]]
[DEFAULT]
enabled_backends=disco
default_volume_type=disco

[disco]
# add you driver configuration here
volume_driver=cinder.volume.drivers.disco.disco.DiscoDriver
volume_backend_name=disco
disco_wsdl_path=/usr/cloudos/dms/conf/DISCOService.wsdl

# Use post-extra because the tempest configuration file is
# overwritten with the .sample after post-config.
[[post-extra|\$TEMPEST_CONFIG]]
[compute]
build_timeout=300

[volume]
storage_protocol=disco
vendor_name=ITRI
backend_names=disco
build_timeout=300

[volume-feature-enabled]
backup=False
EOF
-------------------------------------------------------

Before this commit, these config will take effect it tempest.conf.
After this commit, tempest.conf will change to default config.

It works before.

Success Build
devstack log
http://188.166.245.68/97/382097/20/check/dsvm-tempest-ITRI-DISCO-cinder-driver/5ecc4af/logs/devstacklog.txt.gz
Tempest config
http://188.166.245.68/97/382097/20/check/dsvm-tempest-ITRI-DISCO-cinder-driver/5ecc4af/logs/tempest_conf.txt.gz

Fail Build :
devstack log
http://188.166.245.68/32/332032/18/check/dsvm-tempest-ITRI-DISCO-cinder-driver/da3ed3c/logs/devstacklog.txt.gz
Tempest config
http://188.166.245.68/32/332032/18/check/dsvm-tempest-ITRI-DISCO-cinder-driver/da3ed3c/logs/tempest_conf.txt.gz

[Markus Zoeller (markus_z) (mzoeller)]

Yep, affects our CI https://wiki.openstack.org/wiki/ThirdPartySystems/IBM_zKVM_CI too.

[Markus Zoeller (markus_z) (mzoeller)]

I forgot to mention, our CI tests Nova.

[Markus Zoeller (markus_z) (mzoeller)]

https://review.openstack.org/#/c/405117/1 could fix this by introducing a new phase. This change would still make it necessary that 3rd party CIs which used the post-extra phase for configuration have to change their setup.

[Michal Ptacek (michalx-ptacek)]

Problem is also affecting our CI
https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/405446
Committed: https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=8bf8c8f3810766d19b92f9cb21231095beca30c6
Submitter: Jenkins
Branch: master

commit 8bf8c8f3810766d19b92f9cb21231095beca30c6
Author: Sean Dague <email address hidden>
Date: Thu Dec 1 10:24:06 2016 -0500

    Add test-config local.conf processing

    We need a local.conf processing phase after every run phase which lets
    us override config options after that point. We didn't explicitly
    support this for test-config before, which broke some CI systems when
    we moved tempest to use this later phase.

    Closes-Bug: #1646391

    Change-Id: I7d693afa19acf3e8231e84e45b7a868628ebdbc0

[Sean Dague (sdague)]

We've now added a test-config local.conf section, so folks should adapt their testing configs to use:

[[test-config|$TEMPEST_CONF]]
....

Instead of

[[post-extras|$TEMPEST_CONF]]

....

Then things should work again.