As tempest.scenario.manager was announced stable interface in Tempest 27.0.0[1]
it can be now reused in plugins.
Barbican tempest plugin still uses nova-network old interface for floating ip
related methods, this patch removes them and use tempests's ones which
already use neutron's interface.[2]
Replaced/Removed methods:
* _default_security_group
* _create_security_group
* _create_loginable_secgroup_rule
* _create_security_group_rule
Etherpad concerning this effort:
https://etherpad.opendev.org/p/tempest-scenario-manager-cleanup
[1] https://docs.openstack.org/releasenotes/tempest/v27.0.0.html#release-notes-27-0-0
[2] bbc9dd34f6
Change-Id: I7605fe11caa8ae5725e0c0583c623ebad73d40da
Follow-up of I05b0200b80d8ae957caaa53d5006b050d2d49da6
which fixes also the other leftover usage of a legacy
encryptor class (plain this time).
Change-Id: I8fc4e2e6ed84bf18a4c89c30ee5c40b743d00e46
This patch adds a gate to test the new secure-rbac policy.
Currently, Tempest is unable to create system admin credentials
when the isolated networks option is set to true, so we disable
that option for this gate.
This patch also includes fixes needed to get the existing tests
to pass, as well as some skips for scenario tests that require
isolated networks.
We should be able to remove the skips once Tempest is fixed to
work with system admin.
Depends-On: I584f7b67f2f95caa7c4db3d9d9222d0a9d38442d
Change-Id: I0129ab6d15bc42d98a19e3551b8d009f9ad05e10
Ceph does not support Provider plain.
Volume driver reported an error: Provider plain not supported
Change-Id: If14e6abbf4baf58bda31a476b126bcc18987fc32
1. Tempest has an option CONF.compute.compute_volume_common_az to make
sure that Volume and Instance are created in common AZ If Availability
zones are used. The paramater is respected when instance is created
because tempest.common.compute.create_test_server() is used but not
respected when volume is created for test purpose. Let's make sure
AZ is set when volume is created if parameter is set.
2. The plain Encryptor provider is not support on ceph backends, the
test test_encrypted_cinder_volumes_cryptsetup fails on:
cinder.exception.VolumeDriverException: Volume driver reported an error:
Provider plain not supported.
This comes from [1] which is called in [2]. The Plain provider will be deprecated
in future completely.
[1] https://opendev.org/openstack/cinder/src/branch/master/cinder/volume/volume_utils.py#L1195
[2] https://opendev.org/openstack/cinder/src/branch/master/cinder/volume/drivers/rbd.py#L877
Change-Id: Ib6290ed1ad5779e4e6fed449f3335dbdada42f0d
... instead of the encryptor classes, whose direct usage has been
deprecated since Ocata.
See also Id221414d74af8413084c7935b762f93b7ce43c42 which applied
those changes to tempest.git.
Change-Id: I05b0200b80d8ae957caaa53d5006b050d2d49da6
Cinder volume delete [1] is executed during resource cleanup.
So, if test fails due to some reason then it tries to delete a volume
which is "in-use" state. Detach volume should be executed before
trying to delete the volume. This patch adds nova_detach volume
as a cleanup task.
[1] a6d945d8e6/barbican_tempest_plugin/tests/scenario/manager.py (L229)
Change-Id: I3457bb6fc22a7bb6a32c8d6f4ea5879aeb8d43c5
Related-Bug: #1755485
This should help to isolate failures that are generic from specific test
failures related to barbican. If a test can't pass simple connectivity
check, it's probably broken, and there is no point to attach disks,
because it won't work.
Related-Bug: #1742936
Change-Id: I96cd35392f638c0e5b668f4f3b15cf4cd6114b71
DeprecationWarning: Function 'tempest.test.services()' has moved to
'tempest.common.utils.services()' in version 'Pike' and will be
removed in a future version
Change-Id: Icc6409fcd140406b36a6a84dfa16de8a879cc3b2
Zuul
yatin