Remove testscenarios usage from test_server_basic_ops
This commit removes the scenario test wrapper around
test_server_basic_ops. This has always caused problems in tempest as
it actually tries to do real operations during discovery which is a
terrible idea. This weighed against a very limited benefit and limited
use by most people it's time to just call the experiment and remove
it. This is not saying there is no usefulness in testing a full matrix
of images and flavors on a real deployment, but instead that the place
for this kind of testing is not in tempest discovery. If people who
found this valuable in the past want to retain the functionality should
help work on an alternative method of doing it that isn't so invasive.
Change-Id: Ie7814bd50f1c57c5f8da8355f665f09c9ac8e2d9
diff --git a/releasenotes/notes/remove-input-scenarios-functionality-01308e6d4307f580.yaml b/releasenotes/notes/remove-input-scenarios-functionality-01308e6d4307f580.yaml
new file mode 100644
index 0000000..4ee883f
--- /dev/null
+++ b/releasenotes/notes/remove-input-scenarios-functionality-01308e6d4307f580.yaml
@@ -0,0 +1,11 @@
+---
+upgrade:
+ - The input scenarios functionality no longer exists in tempest. This caused
+ a large number of issues for limited benefit and was only used by a single
+ test, test_server_basic_ops. If you were using this functionality you'll
+ now have to do it manually with a script and/or tempest workspaces
+deprecations:
+ - All the options in the input-scenario group are now deprecated. These were
+ only used in tree by the now removed input scenarios functionality in
+ test_server_basic_ops. They were only deprecated because there could be
+ external consumers via plugins. They will be removed during the Ocata cycle.