Verify-config does not accept a config-file option

Bug #1719459 reported by Ben Kero on 2017-09-25
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

The tempest 'verify-config' command does not accept a --config-file tempest.conf option similar to the 'run' command.

This results in me having to copy config files around to validate them before putting them into production. Obviously this is not ideal.

Ben Kero (ben-kero) on 2017-09-25
description: updated
summary: - Config-validate does not accept a config-file option
+ Verify-config does not accept a config-file option
description: updated
Martin Kopec (mkopec) wrote :


tempest verify-config doesn't have --config-file argument. The tool is workspace aware, so it uses config file located in ./etc/ .. if you want to point the tool to other config file, located in a different location, you can use environment variables TEMPEST_CONFIG_DIR and TEMPEST_CONFIG

Here is the documentation for that:

For now, I'm marking this as Invalid. If you're still having problems, please, provide more information and change the status of the bug to New again.

Changed in tempest:
status: New → Invalid
Matthew Treinish (treinish) wrote :

So while I agree there is workspace support and you can use the env vars to workaround this. I feel this is still a valid bug.

For a cli tool that verifies whether a config file works to not having support to pass in an arbitrary config file path with a cli flag is kinda weird. Especially for when you're creating a config file outside outside of a workspace or a dir named etc/. It's not unreasonable to assume that people want to pass a config file in from the cli.

Changed in tempest:
importance: Undecided → Low
status: Invalid → Triaged
Martin Kopec (mkopec) wrote :

Yes, it would more useful, if a user can pass a config file from CLI. There was an attempt to do it, see the following bug [1], but due to the current design, this small change/addition would require a lot of big changes.


To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers