The stable/2023.2 release was already created so we should start
testing it. Also stable/yoga already passed the end of its extended
maintenace phase and is no longer supported by latest tempst.
Change-Id: If54ec0211e7467583690144fdf450f89e06987fc
As 2023.1 is released, we should add its job on master
gate to keep branchless tempest plugins compatible
to stable branch.
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: Ia8f73e9fa07cbfaea5024047c650dfe5ca747420
Each scenario job is splitted in scenario-traffic-ops and
scenario-non-traffic-ops jobs to avoid possible TIMEOUT in the CI.
Change-Id: Ib8af2af6696b27879eb923793959837646469905
Because octavia-tempest-plugin is branchless, job definitions need to
work for all octavia branches >=wallaby. Older branches should not use
the definitions from current master.
Change-Id: Ic76288560086d225fa59aee399cd75ae4c459559
There has been a direction change in the "secure-RBAC" goal and scoped
tokens are no longer being implemented[1].
The Octavia tempest tests were updated for the new keystone roles and
scoped tokens at the same time with an (bad) assumption that they would be
turned on at the same time.
This patch updates the Octavia tempest plugin to not assume that scoped
tokens are in use when the RBAC type is set to keystone_default_roles.
[1] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rbac.html#direction-change
Depends-On: https://review.opendev.org/c/openstack/octavia/+/877433
Change-Id: Ia1c4ca0b675d39bd43640184d6d3deba823fd3f6
The duration of the c9s scenario job is really close to the max timeout
in Zuul, spliting it into 2 jobs would reduce the duration of the tests
and would avoid possible timeouts.
Change-Id: I3b70171624e5c42fd6055d73a040704af5910944
Thie commit removes jobs for EOM branches (victoria), and the
spare-pool job for branches that no longer support it
Note: some tls-barbican-stable jobs are still referenced by the barbican
project.
Change-Id: If1a951999d95332b879bfe0f26ec584d0b077165
We have stable/yoga released and stable/ussuri is in
'Extended Maintenance' state. Current 'Maintained'
stable branches are yoga, xena, wallaby, and victoria.
As per tempest stable branch testing policy[1], adding the
newly released stable/yoga job and remove the EM stable/ussuri
job.
[1] https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: I96ef69c79014c95e07a5b3848bf50485eaa46df5
Add octavia-v2-dsvm-scenario-centos-9-stream
Add extra args to the "scp" command to authorize the pubkey exchange
with a cirros VM.
Detect the openssh client version to enable the use of the SCP protocol
(starting with openssh 8.7, the SFTP protocol is the default protocol
with scp, SFTP is not supported by Cirros) when sending files to the
cirros VM.
Depends-On: https://review.opendev.org/828189
Change-Id: I689a50e6762fd22e1aaec8aa84ff5b075ff5bd45
We have stable/xena released so we should add
their job on master gate to keep branchless tempest
plugins compatible to stable branch.
This also removes the stable/train job as that is in EM
state now.
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: Ia1ecf95d269af2f6edbd562f31fb69c2cc884cf0
noop-api tests have been frequently timing out since SQLAlchemy
1.4 release.
An analysis showed that some tests are 55% slower with 1.4, but we
haven't fixed it or improved the code yet. To unblock the gates, set the
timeout to 10800 sec (3h00) for those jobs. We might revert this commit
when we figure out how to improve test exec times.
Change-Id: I68a5357f58b74f0f759cab0bb89a517c384d05e0
Two-node job was failing because devstack tried to compile the
test_server.go file on controller2.
controller2 doesn't have tempest installed, but octavia-tempest-plugin
was installed. The compilation step was failing and is not necessary
there.
Fix octavia-v2-act-stdby-dsvm-scenario-two-node definition, overrides
were not applied.
Fix the "zuul_copy_output" section.
Move to ML2/OVN backend.
Co-Authored-By: Carlos Goncalves <cgoncalves@redhat.com>
Change-Id: I24976e93e9ea8f7f50c9da014c2627965512893c
This patch refactors the RBAC enforcement checks in the API tests.
It also updates those test for keystone scoped tokens and default roles.
Change-Id: I6fad03f5a89c213562918ca258884aac34ba7ce7
Stein release of Octavia has reached end-of-life (EOL) support [1].
The stable/stein Octavia branch no longer accepts changes.
We can now remove the Stein CI jobs.
[1] https://review.opendev.org/c/openstack/releases/+/772847
Change-Id: I14ab0f8b159fdd0c7e81b94297a57f30260579fa
The name of the OVN provider job template changed from
ovn-octavia-provider-v2-dsvm-scenario to
ovn-octavia-provider-tempest-release but was not updated
here, fix it so those non-voting jobs will run.
Change-Id: I3159adeae2456c8fecad87bbfb0f526363e7752b
With octavia_create_network_interface_device() being in
the neutron tree, we have to enable the neutron plugin
in more jobs to have it visible, else o-hm0 will not
get created and it will fail.
Moved the occurence in the ipv6-only job to the parent
definition as well.
Change-Id: I0d15dbae9034ab17de69d884e8f57df0d25d4338
A recent patch lowered the swap space available on nodepool
instance from 8GB to 1GB. This is causing nova to not have enough
memory to boot VMs required for some tests.
This patch restores the 8GB swap value for these jobs.
[1] https://review.opendev.org/#/c/750941/
Change-Id: I19c3465fb39a6204a5a167ac75b6eed832f9fe72
Every time we update the Go test server code, we have to re-compile it
locally and commit the binary file. Git is not great for binary blobs.
One other reason that carrying the binary in-tree is suboptimal is it
is compiled against amd64 architecture, thus not much multi-arch
friendly.
This change drops the need to compile and carry the test server binary
file in the Git tree. The test server will now be compiled at devstack
test-config phase. On my work station, it takes less than 6 seconds.
Change-Id: I3d8ad18ddd1f23720618d733a9d8a53a6b4e6dfc
Wait for the loadbalancer to become ACTIVE after deleting an
healthmonitor or a listener, to ensure the next test uses a LB in a
non-transitional state.
This also fixes the cidrs tests that were using the wrong waiter
timeouts.
This patch also moves individual deletion of children resources in class
tear down to a more performant way by cascade deleting the load
balancer.
Story: 2008219
Task: 41008
Depends-On: https://review.opendev.org/#/c/757604/
Depends-On: https://review.opendev.org/#/c/757840/
Depends-On: https://review.opendev.org/#/c/757841/
Depends-On: https://review.opendev.org/#/c/757842/
Co-Authored-By: Carlos Goncalves <cgoncalves@redhat.com>
Change-Id: I6a4eed7269e4f502bd0fc8613cb4ec4da13890e7
This is a patch to restructure the API tests to use the
new skip_if_not_implemented capability.
Depends-On: https://review.opendev.org/745239
Change-Id: I291488e1c9418e51d6fe7ea142eaca13e3c181a0
This is a patch to restructrue the scenario tests to use the
new skip_if_not_implemented capability.
Change-Id: I49a7fb6650030f2a1115c6d42442062bd33415fd
Production deployments are recommended to run on active-standby
loadbalancer topology and with nova anti-affinity enabled for higher
level of availability. Job octavia-v2-act-stdby-dsvm-scenario-two-node
will test Octavia under such configuration.
Task: 40413
Story: 2007943
Change-Id: Iab24754bf6881671091a06047767f8b4dc8b5420
Takashi Kajinami