The subnet field in metdadata port is incorrectly updated in some cases
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-ovn |
New
|
Undecided
|
Unassigned |
Bug Description
After the following steps, the subnet field in the metdadata port is incorrectly updated, it will contain all subnets regardless of the subnet supports dhcp or not.
1st: Create two subnets in same network, one with enable_dhcp=True and the other with enable_
2nd: Update the first subnet, e.g. updating subnet name
openstack subnet set --name subnet2-new 639659e1-
Then metadata port contains both of the two subnets, that's incorrect.[2]
Seems there are two issues, one is enable_dhcp=[1] is missing in filter and the other is we did not clear the subnets which are disabled.
Issue 1: https:/
Issue 2: https:/
[1]
ovn lsp column:
56c514b1-
stack@c3:
+------
| Field | Value |
+------
| cidr | 10.0.0.64/26 |
| enable_dhcp | True |
| gateway_ip | 10.0.0.65 |
| network_id | 69e1e4d1-
| project_id | 0134078dd4e5400
...
+------
stack@c3:
+------
| Field | Value |
+------
| cidr | 10.0.0.192/26 |
| enable_dhcp | False |
| gateway_ip | 10.0.0.193 |
| network_id | 69e1e4d1-
...
+------
stack@c3:
+------
| Field | Value |
+------
| device_owner | network:dhcp |
| fixed_ips | ip_address=
| id | 790b1d9c-
| network_id | 69e1e4d1-
...
+------
[2]
stack@c3:
+------
| Field | Value |
+------
| admin_state_up | UP |
| device_owner | network:dhcp |
| fixed_ips | ip_address=
| | ip_address=
| id | 790b1d9c-
| network_id | 69e1e4d1-
...
+------