tree 7af57688afc554d8b81e2cb242efd46284ebdc95
parent 8257d9e9c095a6d145217217f5c84edfa29384bc
author Goutham Pacha Ravi <gouthampravi@gmail.com> 1592600062 -0700
committer Goutham Pacha Ravi <gouthampravi@gmail.com> 1592921312 +0000

[ci] Use dynamic credential provider in DHSS=False tests

Manila's tempest tests create test credentials on
the fly using tempest's dynamic test credential
framework. Launchpad bug 1883795 points to an issue
where we're forcing the creation of test accounts dynamically
even when "[auth]/use_dynamic_credentials" has been set
to False. The appropriate fix [0] for that bug is to
skip tests that *require* a new test credential.
This leads us to lose test coverage in such a situation.
Currently, manila tempest tests cannot be run reliably
with dynamic credentials when testing DHSS=True drivers.
See bugs [1][2][3][4]; So these tests use the
pre-provisioned test credentials framework
as a workaround. We plan to fix this soon [5].

In the meantime, we don't want to lose test coverage
by turning off dynamic credentials all the time.

So ensure we're running with dynamic creds turned on
for all test jobs except the DHSS=True jobs. After
[5] merges, we can turn on dynamic credentials
everywhere.

[0] https://review.opendev.org/736195/
[1] https://launchpad.net/bugs/1762900
[2] https://launchpad.net/bugs/1604732
[3] https://launchpad.net/bugs/1607069
[4] https://launchpad.net/bugs/1679715
[5] https://review.opendev.org/728604/

Change-Id: I48c41fd197118e5fd701e9e8056802c8c0895410
Related-Bug: #1883795
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>