yahoo-eng-team team mailing list archive

[shihanzhang <shihanzhang@xxxxxxxxxx>]

Public bug reported:

Now for tunnel network like vxlan or gre in neutron, if we change a
compute node tunnel IP, the obsolete tunnel info was still saved in
neutron-server, and other compute nodes still established tunnel with
the obsolete IP, I think we should provide a approach to clean the
obsolete tunnel info, like ovs_cleanup.py.

** Affects: neutron
     Importance: Undecided
     Assignee: shihanzhang (shihanzhang)
         Status: New

** Description changed:

- Now for tunnel network like vxlan or gre in neutron, if we change a compute node tunnel IP, the obsolete tunnel info was 
- still saved in neutron-server, and other compute nodes still established tunnel with the obsolete IP, I think we should provide a approach to clean the obsolete tunnel info, like ovs_cleanup.py.
+ Now for tunnel network like vxlan or gre in neutron, if we change a
+ compute node tunnel IP, the obsolete tunnel info was still saved in
+ neutron-server, and other compute nodes still established tunnel with
+ the obsolete IP, I think we should provide a approach to clean the
+ obsolete tunnel info, like ovs_cleanup.py.

** Changed in: neutron
     Assignee: (unassigned) => shihanzhang (shihanzhang)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1608347

Title:
  Neutron-server can't clean obsolete tunnel info

Status in neutron:
  New

Bug description:
  Now for tunnel network like vxlan or gre in neutron, if we change a
  compute node tunnel IP, the obsolete tunnel info was still saved in
  neutron-server, and other compute nodes still established tunnel with
  the obsolete IP, I think we should provide a approach to clean the
  obsolete tunnel info, like ovs_cleanup.py.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1608347/+subscriptions