During SRU verification, I was unable to reliably reproduce the reported
neutron-server startup "crash" when configuring multiple DHCP option
values in ovn_dhcp4_global_options.
Upon further analysis, this change primarily affects how DHCP option
values are parsed and translated before being sent to OVN, rather than
consistently triggering a service failure. In particular, the fix
introduces support for multiple values per key (separated by ;) and
ensures they are formatted correctly for OVN (e.g. {val1, val2}).
Given this, I will be updating the Test Plan to validate the behavior
change directly by:
* configuring multiple DHCP option values in ml2_conf.ini
* restarting the neutron service
* creating a network and subnet to trigger DHCP option application
* verifying in the OVN Northbound database that values are correctly formatted
Before applying the fix, multiple values remain unparsed (e.g.
wpad="1.2.3.5;1.2.3.6"). After the fix, these should be rendered in OVN-
compatible list format (e.g. wpad="{1.2.3.5, 1.2.3.6}").
This updated approach will ensure the patched code path is properly
exercised and validated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2126923
Title:
ovn_dhcp4_global_options doesn't support keys with a list of values
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2126923/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
