host not removed from table ml2_vxlan_endpoints with the agent delete
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Triaged
|
Medium
|
Miro Tomaska |
Bug Description
After deleting an agent, there is stale entry for the host in table 'ml2_vxlan_
I have not checked other topologies but same should apply to other similar tables 'ml2_gre_endpoints' and 'ml2_geneve_
# Ensure agent is stopped or node is removed.
$ openstack network agent show 338d13fc-
+------
| Field | Value |
+------
| admin_state_up | UP |
| agent_type | Open vSwitch agent |
| alive | XXX |
| availability_zone | None |
| binary | neutron-
| configuration | {'arp_responder
| | 'devices': 0, 'enable_
| | 'l2_population': True, 'log_agent_
| | ['bareudp', 'erspan', 'geneve', 'gre', 'gtpu', 'internal', 'ip6erspan', 'ip6gre', 'lisp', 'patch', 'stt', 'system', 'tap', 'vxlan']}, |
| | 'ovs_hybrid_plug': False, 'resource_
| | 'resource_
| | {'allocation_
| | {'allocation_
| | 'resource_
| | 'vhostuser_
| created_at | 2023-10-25 14:30:17 |
| description | None |
| ha_state | None |
| host | ykarel-temp3 |
| id | 338d13fc-
| last_heartbeat_at | 2023-10-25 14:30:17 |
| resources_synced | None |
| started_at | 2023-10-25 14:30:17 |
| topic | N/A |
+------
$ openstack network agent delete 338d13fc-
mysql> select * from ml2_vxlan_
+------
| ip_address | udp_port | host |
+------
| 10.0.109.173 | 4789 | ykarel-temp3 | <- Host/Ip entry still exist after the agent delete
| 10.0.109.224 | 4789 | ykarel-temp2 |
| 10.0.109.60 | 4789 | ykarel-temp1 |
+------
3 rows in set (0.00 sec)
The stale entry doesn't caused any issue but it's good to get rid of the host/node references which are removed from the cluster. Stale entries are also seen in table 'segmenthostmap
These left overs were noticed in an older release train https:/
Changed in neutron: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in neutron: | |
assignee: | nobody → Miro Tomaska (mtomaska) |
Also found this old bug[1] which should have fix this issue. But there were few refactors and the issue might have been reintroduced. I will look into it and I will see if there is a way to write a test to prevernt this from regressing again.
[1]https:/ /bugs.launchpad .net/neutron/ +bug/1179223