yahoo-eng-team team mailing list archive

[OpenStack Infra <1279683@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/74228
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=c3d73c82d38a982d2463e7ec9929dad02e2b0550
Submitter: Jenkins
Branch:    master

commit c3d73c82d38a982d2463e7ec9929dad02e2b0550
Author: shihanzhang <shihanzhang@xxxxxxxxxx>
Date:   Tue Feb 18 10:27:02 2014 +0800

    Fix problem of deleting dhcp port
    
    when network is deleted, the dhcp port in that network will be deleted
    automaticly, so '_cleanup_ports' should not clean dhcp port. I already
    have a patch to fix the problem of deleting dhcp port.
    
    Change-Id: I92f90a3dad6d76954d466e4b30ab7c46434ba7df
    Closes-bug: #1279683


** Changed in: tempest
       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/1279683

Title:
  The problem generated by deleting dhcp'port by mistack

Status in OpenStack Neutron (virtual network service):
  In Progress
Status in Tempest:
  Fix Released

Bug description:
  In my environment, I delete the dhcp port by mistack, then I found the vm in primary subnet can not get IP, the reason is that when a dhcp port is deleted, neutron will create the dhcp port automaticly, but the VIF TAP will not be deleted, you will see one IP in two VIF TAP
   
  root@shz-dev:~# ip netns exec qdhcp-ab049276-3b7c-41a2-b62c-3f587a02b0a6 ifconfig
  lo        Link encap:Local Loopback  
            inet addr:127.0.0.1  Mask:255.0.0.0
            inet6 addr: ::1/128 Scope:Host
            UP LOOPBACK RUNNING  MTU:16436  Metric:1
            RX packets:1 errors:0 dropped:0 overruns:0 frame:0
            TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:0 
            RX bytes:576 (576.0 B)  TX bytes:576 (576.0 B)

  tap4694b3c4-a6 Link encap:Ethernet  HWaddr fa:16:3e:41:f6:fc  
            inet addr:50.50.50.2  Bcast:50.50.50.255  Mask:255.255.255.0
            inet6 addr: fe80::f816:3eff:fe41:f6fc/64 Scope:Link
            UP BROADCAST RUNNING PROMISC  MTU:1500  Metric:1
            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
            TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:0 
            RX bytes:0 (0.0 B)  TX bytes:796 (796.0 B)

  tapa546a666-31 Link encap:Ethernet  HWaddr fa:16:3e:98:dd:a7  
            inet addr:50.50.50.2  Bcast:50.50.50.255  Mask:255.255.255.0
            inet6 addr: fe80::f816:3eff:fe98:dda7/64 Scope:Link
            UP BROADCAST RUNNING PROMISC  MTU:1500  Metric:1
            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
            TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:0 
            RX bytes:0 (0.0 B)  TX bytes:496 (496.0 B)

  Even if the problem is caused by error operation, I think the dhcp
  port should not allow be deleted, the port on router can not be
  deleted.

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