yahoo-eng-team team mailing list archive

[Harald Jensås <hjensas@xxxxxxxxxx>]

** Changed in: neutron
       Status: New => Invalid

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

Title:
  routed-networks - segments subnet dhcp port bind to wrong segment

Status in neutron:
  Invalid

Bug description:
  $  openstack network list -f json
  []
  $ openstack network create ctlplane

  Network created, and we have 1 default segment:

  $ openstack network segment list --network ctlplane -f json
  [
    {
      "Network": "89e4aa6c-06f2-4348-9576-bec17c7526d6", 
      "Network Type": "local", 
      "Segment": null, 
      "ID": "46950790-717b-4d31-883a-a8d9d3df2e92", 
      "Name": null
    }
  ]

  $  openstack network segment create subnet0 --physical-network
  ctlplane --network ctlplane --network-type flat

  $ openstack subnet create --subnet-range 172.20.0.0/26 --dhcp
  --gateway 172.20.0.62 --ip-version 4 --network ctlplane --network-
  segment subnet0 --allocation-pool start=172.20.0.10,end=172.20.0.19
  subnet0

  
  (undercloud) [stack@ocataleafs ~]$ sudo ip netns list
  qdhcp-89e4aa6c-06f2-4348-9576-bec17c7526d6
  (undercloud) [stack@ocataleafs ~]$ sudo ip netns exec qdhcp-89e4aa6c-06f2-4348-9576-bec17c7526d6 ip addr show | grep tap
  13: tap0170296c-f2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000
      inet 172.20.0.10/26 brd 172.20.0.63 scope global tap0170296c-f2
  (undercloud) [stack@ocataleafs ~]$ sudo ip netns exec qdhcp-89e4aa6c-06f2-4348-9576-bec17c7526d6 ping 172.20.0.62
  PING 172.20.0.62 (172.20.0.62) 56(84) bytes of data.
  From 172.20.0.10 icmp_seq=1 Destination Host Unreachable
  From 172.20.0.10 icmp_seq=2 Destination Host Unreachable

  $ openstack network segment list -f json
  [
    {
      "Network": "89e4aa6c-06f2-4348-9576-bec17c7526d6", 
      "Network Type": "local", 
      "Segment": null, 
      "ID": "46950790-717b-4d31-883a-a8d9d3df2e92", 
      "Name": null
    }, 
    {
      "Network": "89e4aa6c-06f2-4348-9576-bec17c7526d6", 
      "Network Type": "flat", 
      "Segment": null, 
      "ID": "32a308e9-6f2e-4252-a273-95c7bfbcc94e", 
      "Name": "subnet0"
    }
  ]
  (undercloud) [stack@ocataleafs ~]$ openstack network segment delete 46950790-717b-4d31-883a-a8d9d3df2e92
  Failed to delete network segment with ID '46950790-717b-4d31-883a-a8d9d3df2e92': HttpException: Conflict (HTTP 409) (Request-ID: req-8b1a5179-c987-47ba-b35a-68c9afdca4bc), Segment '46950790-717b-4d31-883a-a8d9d3df2e92' cannot be deleted: The segment is still bound with port(s) 0170296c-f2e5-4482-843a-3ebb0bf11381.
  1 of 1 network segments failed to delete.


  The dhcp-namespace port did not bind to the segment associated with
  subnet0, it bound to the default segment that is automatically created
  when creating a network.

  If I change the workflow to first delete the default segment, and then
  create segment: subnet0 + subnet: subnet0 the dhcp namespace is wired
  correctly.

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