Comment 6 for bug 1817154

I agree with tosky. none of the repo/plugins should register the duplicate config option.

There are many tempest-plugin like congress etc which need to check some other plugin service_availability. So they check the service presence in their devstack plugin and then set the service_availability of that service in tempest.conf. Note, they only set the value of that config option but do not register. registry of config options has to be done in own plugin only.

What Octavia can do here is, check the presence of CONF.service_available.barbican and if that config option is not registered/available then, consider that Barbican is not available and skip the test/operation. For example[1].

Setting of value can be handled via devstack plugin as service_available.barbican is default to false in barbican-tempest-plugin [2]

[1] https://github.com/openstack/congress-tempest-plugin/blob/4390716a373b67a85fadc743495494bd18679b63/congress_tempest_plugin/tests/scenario/congress_datasources/test_mistral.py#L31

[2] https://github.com/openstack/barbican-tempest-plugin/blob/123dd7d4162c39a1cb4b4c1b09a5dceaee127eb6/barbican_tempest_plugin/config.py#L19