Removing sahara from the service available group
This is a leftover from when sahara was moved out of tree.
It causes conflicts when the sahara plugin loads, and it should
be removed.
This option is not used right now by Tempest code, so even if someone
is using it, it has not effect whatsoever on test execution.
The only case in which this option may have effect, is when the
sahara-tests Tempest plugin is installed. When the
sahara plugin is loaded, the config option will be there.
I think in this case we should skip deprecation, and just remove it
like we did in the past when moving Tempest code to a plugin.
Change-Id: Ie7556b97237b0101000d140d351edea5e518783f
diff --git a/releasenotes/notes/remove-sahara-service-available-44a642aa9c634ab4.yaml b/releasenotes/notes/remove-sahara-service-available-44a642aa9c634ab4.yaml
new file mode 100644
index 0000000..c0dc7d7
--- /dev/null
+++ b/releasenotes/notes/remove-sahara-service-available-44a642aa9c634ab4.yaml
@@ -0,0 +1,7 @@
+---
+fixes:
+ - |
+ The 'sahara' config option in the 'service-available' group has been moved to the sahara plugin
+ (openstack/sahara-tests) along with tests and service client during the Ocata timeframe.
+ A 'sahara' config option was left over on Tempest side, and it's removed now.
+ As long as the sahara plugin is installed, this change as no impact on users of sahara tests.