Reviewed: https://review.opendev.org/c/openstack/neutron/+/864715 Committed: https://opendev.org/openstack/neutron/commit/686698284b3553001398f65614c6521359bc45aa Submitter: "Zuul (22348)" Branch: master
commit 686698284b3553001398f65614c6521359bc45aa Author: hailun.huang <[email protected]> Date: Wed Nov 16 09:35:22 2022 +0000 Update tap ip in metadata agent when metadata port ip updated Update neutron-ovn-metadata-agent, catch port_binding update event of monitoring localport type, and judge if the neutron:cidrs field in the external_ids of port_binding table has changed, then update_datapath. Closes-Bug: #1996677 Change-Id: Ibdc1b385b07a2ab1ca8e4b6278f6d39fb5839509 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1996677 Title: [OVN] support update fixed_ips of metadata port Status in neutron: Fix Released Bug description: In some scenarios, the customers want to modify the fixed_ips of metadata port. We can workaround it by follow steps: 1.Fisrt, update fixed_ips of metaadta_port: neutron port-update --fixed-ip subnet_id=e130a5c7-6f47-4c76-b245-cf05369f2161,ip_address=192.168.111.16 460dffa9-e25a-437d-8252-ae9c5185aaab 2.Then, only trigger subnet updated: neutron subnet-update --enable-dhcp e130a5c7-6f47-4c76-b245-cf05369f2161 3.Finally restart neutron-ovn-metadata-agent I think it is a good requirement that support update fixed_ips of metadata port. Maybe we can implement it in neutron-ovn-metadata-agent that watching the UPDATE event of port_bidnings, and then update_datapath if row is related to metadata port. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1996677/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
