yahoo-eng-team team mailing list archive

[yanghongyu <1834979@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Pre-conditions: 
    Neutron （Pike）,firewall_driver=openvswitch

Reproduction steps:
    1.create vm-A with net-A
    2.shutoff vm-A
    3.show port status of vm-A 
    4.update net-A ，change its name to 'net-A-rename'
    5.show port status of vm-A

Description:
    After step 2,we can find the port status of vm-A is down,and at this moment there is no related tap device in br-int.This make sense.
    But,after step 4,the status became active,there is still no tap device,and vm-A still shutoff.This doesn't make any sense.We just change network name.This behavior has no relation to port status .
    According to code,we find that DHCP agent (_dhcp_ready_ports_loop->dhcp_ready_on_ports)will notify neutron server to make ports active each time after network,subnet,port,updated.Why this logic?

Any ideas?

** 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/1834979

Title:
  port status became active after update network，subnet

Status in neutron:
  New

Bug description:
  Pre-conditions: 
      Neutron （Pike）,firewall_driver=openvswitch

  Reproduction steps:
      1.create vm-A with net-A
      2.shutoff vm-A
      3.show port status of vm-A 
      4.update net-A ，change its name to 'net-A-rename'
      5.show port status of vm-A

  Description:
      After step 2,we can find the port status of vm-A is down,and at this moment there is no related tap device in br-int.This make sense.
      But,after step 4,the status became active,there is still no tap device,and vm-A still shutoff.This doesn't make any sense.We just change network name.This behavior has no relation to port status .
      According to code,we find that DHCP agent (_dhcp_ready_ports_loop->dhcp_ready_on_ports)will notify neutron server to make ports active each time after network,subnet,port,updated.Why this logic?

  Any ideas?

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