yahoo-eng-team team mailing list archive

[Liu Xie <1996677@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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 updating:
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.

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
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:
  New

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 updating:
  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