the removal of the Sahara tests from Tempest  broke the tests now in
sahara-tests, and basically I underestimated the fall-out of the removal.
Apart from a minor issue due to the wrong exception , the key issue comes
from the option groups in tempest.conf, which are defined as data-processing
and data-processing-feature-available, while the code tries to access
CONF.data_processing. Previously this was handled by some magic mapping ,
which can't be used, as it is, by plugins.
I came up with this solution  after discussing with Andrea Frittoli. The
patches only fails with the automation negative tests, which are on the way of
the Dodo anyway .
The alternative fix for sahara would involve patching the configured
tempest.conf in few branches, in addition to the fixes to sahara-tests, and
I'd frankly prefer a more general solution.
My question is: can you please approve  and , so that Sahara gates can
OpenStack Development Mailing List (not for usage questions)