In prior changes we restricted the execution around tempest
plugin tests designed to exercise various configurations
and scenarios. We've since updated the tempest test to
choose and dial back the duplication of execution and
it just so happened this job excluded the test which would
have run while the remaining job auto-excluded itself.
Now, the plugin makes the right decision, and there is no need
to define an exclusion in the job config.
Change-Id: Ifc27c8c6cf45a753ca98e710394f6c98d45307b2
Signed-off-by: Julia Kreger <juliaashleykreger@gmail.com>
349782499d