Since Iaca6fd3e6ed3c64ab3ca22817ad461479ecfa189, _verify_http_connection
is no longer used anywhere. Its removal also exposes two more utils
functions that are also not used anywhere.
Change-Id: I88423b89f30ef2c4cb4738bbee1246e019796d73
When a test fails, it's helpful to see what was on the console when it
did. For example, if `nc` failed to start.
Change-Id: I36d1cd5a04691c09fb0d7c330444ae4a50bfe264
This reverts commit 7c4473d55c31f147154cc60487859e5db05ab5e9.
Reason for revert: Should be fixed on the Designate side with
the Depends-on patch.
Depends-On: https://review.opendev.org/c/openstack/designate/+/927792
Change-Id: If549f21a38def48d094adea6cbfaa67f1855da17
This patch adds admin API tests for the trusted attribute of the port
resources. Tests are checking if port created with 'trusted' attribute
set have it set correctly in 'trusted' attribute and in the
binding:profile. Second test checks the same but using update port API
call.
Depends-On: https://review.opendev.org/c/openstack/neutron/+/926068
Related-Bug: #2060916
Change-Id: Idcadaed240f156312fbe38eb9b20c9699eea3282
neutron-tempest-plugin-designate-scenario is failing 100%
with the designate new RBAC
- https://review.opendev.org/c/openstack/neutron/+/926085
This job is non voting on neutron side but voting on designate
side. And merging the requirement change
(https://review.opendev.org/c/openstack/requirements/+/925464),
will break the designate gate.
Making this job non voting for everyone until we figure out the
root cause of this failure.
Related-Bug: #2078518
Change-Id: If0f521a74ce075b408b5495a0144f01e3bcbc818
It's disabled for ovn because it's not, yet, implemented for the driver.
See: https://review.opendev.org/c/openstack/neutron/+/926495
(The feature also requires special configuration for the driver that we
probably won't enable in the gate. This can be discussed though.)
Related-Bug: #2051935
Change-Id: Ie2e49a53857009446e22300e2fff292355cef058
Since the tests running in parallel, when resources
are deleted by concurrent tests, GET call can return
0 resources, adjust tests to not fail when there are
0 items returned.
This is in continuation of previous patch[1].
[1] https://review.opendev.org/926201
Related-Bug: #2076328
Change-Id: I37c1a3855cb5c37aadec5cda26c89cd3f99e074f
This reverts commit 74a78a4b4d7a966c67bab323191c3658ef943c58.
Reason for revert: Bug #2068727 resolved by switching back to eventlet.
Change-Id: I5d979a7313ab24d8b9101a37a3ed8d080569d7c3
Related-Bug: #2068727
It seems that sfc job is failing due to some RPC message timeouts when
running Neutron with uwsgi so lets switch it to the eventlet for now to
make that scenario job to be green finally.
Related-bug: #2068727
Change-Id: I2d13095bdc57cf1c5d8d1c9a90e4ca862094c0c5
This change enables the testing of querying the metadata service over an
IPv6 only network
Depends-On: https://review.opendev.org/c/openstack/neutron/+/922264
Change-Id: I56b1b7e5ca69e2fb01d359ab302e676773966aca
Related-Bug: #2069482
Closes-Bug: 2076916
When running tempest with higher concurrency, pagination tests
randomly fails as returned resources also include resources
created from other concurrent tests.
Filtering the returned results with names should help.
Closes-Bug: #2076328
Change-Id: I72de57cc382bb06606187c62b51ebb613f76291c
In the test_router_interface_fip test module there was probably some
copy paste error which was checking if revision_number key exists in the
older response from the API then what was used in the assertion.
Now this is fixed.
TrivialFix
Change-Id: Ica10dfec9bb806c3dca2f0a2e0aff36006c9c092
Since [1] linuxbridge and openvswitch jobs are randomly
failing as swap gets fully utilized and processes are
getting oom-killed, to avoid this increasing swap size
to 3GB.
[1] https://review.opendev.org/c/openstack/devstack/+/924094
Closes-Bug: #2073582
Change-Id: I3889beb4c3427dd14ba1d1cddc9027b366268c1b
This can be reverted once related bug will be fixed. For now lets
unblock our gate by making this job non-voting.
This job is not running in the gate queue neighter in
neutron-tempest-plugin nor neutron gate.
Related-bug: #2072627
Change-Id: Icab69e12c71d384d4573ca56154fc3812b6355c2
All the ML2/OVS jobs in master branch (Dalmatian 2024.2) are now using
the WSGI API module, instead of the eventlet server.
Related-Bug: #2069581
Topic: eventlet-deprecation
Change-Id: Iff105f644459b56ece054bdefb294b1c6da143f5
This method retrieves the extensions loaded by the Neutron API, instead
of reading the configured extensions in the tempest configuration.
This method can help during a extension implementation, as for example
in "subnet-external-network". This extension cannot be declared yet in
the neutron-tempest-plugin job definitions, because the extension has
not been implemented in Neutron. However, when the Neutron patch is
tested, the extension is missing in the configuration and the test
cannot correctly modify the API calls.
Related-Bug: #2051831
Change-Id: I3e6f570cd63e44df7ceb8f5013c2b4adebfe4286
Add experimental jobs for OVS and OVN with wsgi.
The same jobs can be used in the Neutron periodic queue.
Depends-On: https://review.opendev.org/c/openstack/devstack/+/922012
Change-Id: I5a3bdcb0b7c399fed01bf08e211eb572edcd8d74
Using 'files:' section to always trigger the designate
scenario tests is incorrect. Change irrelevant-files
section to just ignore all the other services/*
directories instead until we figure out a better way.
Change-Id: I12bd45da7b76fb06e922fa50c86d5abba434a3c8
Commit c76727b97c040 broke the gate by causing jobs
to not get run when it added RE2 compatibility for
irrelevant files. Digging found that RE2 doesn't
support negative lookahead (and won't ever). This
fixes the issue by just not including the single
file we care about in each section.
[0] https://github.com/google/re2/issues/156
Change-Id: I6f8445bcd2a409cc0e85943b7d20ce578e37dd55
