[CI] Stop gating with manila-tempest-minimal-dsvm-lvm
The job manila-tempest-minimal-dsvm-lvm is functionally
identical to manila-tempest-minimal-dsvm-lvm-ipv6-only.
Semantically, the only difference being that the service
host, and in turn the endpoint base for manila, and the
communication address for rabbitmq, mysql and other infra
services.
manila-tempest-minimal-dsvm-lvm-ipv6-only
has MANILA_SERVICE_HOST set to an IPv6 address,
for example:
MANILA_SERVICE_HOST='[::1]'
MANILA_ENDPOINT_BASE='http://[::1]:8786'
manila-tempest-minimal-dsvm-lvm has MANILA_SERVICE_HOST
set to an IPv4 address, for example:
MANILA_SERVICE_HOST='23.253.236.222'
MANILA_ENDPOINT_BASE='http://23.253.236.222:8786'
So lets drop the job enforcing IPv4 service host since
we have coverage for that scenario in other jobs that
we're running, including the voting
manila-tempest-minimal-dsvm-dummy job.
I'd like to backport this change to stable/train
during which this job was duplicated to cover the scenario
of doing "ipv6-only" service host testing [1]
[1] https://review.opendev.org/#/c/682716/
Change-Id: I51dc25889c1d1fb361f0be6f8c0aa47ca64c9aaa
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
(cherry picked from commit 14d081acf6
)
This commit is contained in:
parent
678ea79f85
commit
93102287f8
|
@ -32,7 +32,6 @@
|
|||
- manila-tempest-minimal-dsvm-dummy
|
||||
# Through the Train release we need to keep some python2 coverage.
|
||||
- manila-tempest-minimal-dsvm-dummy-py2
|
||||
- manila-tempest-minimal-dsvm-lvm
|
||||
- manila-tempest-minimal-lvm-ipv6-only
|
||||
- manila-grenade:
|
||||
voting: false
|
||||
|
@ -50,7 +49,6 @@
|
|||
jobs:
|
||||
- manila-tox-genconfig
|
||||
- manila-tempest-minimal-dsvm-dummy
|
||||
- manila-tempest-minimal-dsvm-lvm
|
||||
- manila-tempest-minimal-lvm-ipv6-only
|
||||
experimental:
|
||||
jobs:
|
||||
|
|
Loading…
Reference in New Issue