Skip to content

Conversation

@github-actions
Copy link

This PR contains a snapshot of 2025.1 from upstream stable/2025.1.

elvgarrui and others added 5 commits October 22, 2025 09:59
We have 2 classes inheriting from BaseNeutronAgentOSKenApp:
OVSNeutronAgentOSKenApp and OVSLogOSKenApp. The instantiation of
packet_in_handlers as a static property in BaseNeutronAgentOSKenApp
created a shared list between all the different objects created by the
inheriting classes. This ended up creating duplicated processing of
events and therefore duplicate logging in the ML2/OVS log API.

Closes-Bug: #2121961

Change-Id: I6c37fbed8d724b7215ca21d155dde00e1229c6ea
Signed-off-by: Elvira Garcia <[email protected]>
(cherry picked from commit 29f4ada)
Enable the deletion of all the Designate recordssets for the same
dns_name and dns_domain associated with the specified IP
addresses.

This change enables in the Designate driver the separate deletion
of two recordsets associated to the same dns-name and dns-domain
that were created by a sequence of one port create/update and one
floating ip create/update. Before this change, the assumption when
deleting recordsets associated to the same same dns-name and
dns-domain was that they were created in a single operation.
Consequently, the change handles each deletion operation of the
dns_name in the dns_domain based on the IP addresses specified
in the input argument.

Existing unit tests in test_dns_integration.py and
test_dns_domain_keywords.py failed with this change.  These existing
test cases are updated in this commit such that the IP addresses
in the mock recordsets are strings, instead of netaddr.IPAddress()
objects, to match recordset['records'] data type in
_get_ids_ips_to_delete().  The unit tests passed with mismatched
types in the past because the check between recordset and input
argument records compared the size of two sets rather than the
values of the data.

A new unit test test_delete_single_record_from_two_records() is
added to test that the designate driver handles the use case where
only a subset of A or AAAA records are deleted.
test_delete_single_record_from_two_records() was generated with the
assistance of Claude Code, copying from test_delete_record_set()
with a small modification to delete only one of the records.

Assisted-by: Claude Code
Depends-on: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/960659
Closes-Bug: #2115776
Change-Id: I42f1d504a063f1d8542c861b3b7caffe56c47bf1
Signed-off-by: Helen Chen <[email protected]>
(cherry picked from commit 9320cd3)
tempest master dropped the python3.9 support in [1], so
we need to use tempest 45.0.0 which last version supporting
python3.9.

[1] https://review.opendev.org/c/openstack/tempest/+/966101

Related-Bug: #2130551
Signed-off-by: Yatin Karel <[email protected]>
Change-Id: Ia0bbb62119621d2cb5781a6e12bf1f2afab1d72e
@github-actions github-actions bot requested a review from a team as a code owner November 17, 2025 06:23
@github-actions github-actions bot added automated Automated action performed by GitHub Actions synchronisation labels Nov 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated Automated action performed by GitHub Actions synchronisation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants