yahoo-eng-team team mailing list archive

[Armando Migliaccio <1373660@xxxxxxxxxxxxxxxxxx>]

This is a massive non-backward compatible change, with a massive impact
on the existing codebase (as the same rule should be applied across all
service ports). During the drivers meeting [1] some of us felt strongly
against this one, so for this reason, we'll mark as won't fix.

[1]
http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-11-24-15.01.log.html

** Changed in: neutron
       Status: Triaged => Won't Fix

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

Title:
  [RFE] An in-use dhcp port can be deleted

Status in neutron:
  Won't Fix

Bug description:
  An in-use dhcp-port can be deleted by a tenant:

  For example:

  
  stack@Controller:~/DEVSTACK/user-1$ neutron net-list
  +--------------------------------------+-----------+--------------------------------------------------+
  | id                                   | name      | subnets                                          |
  +--------------------------------------+-----------+--------------------------------------------------+
  | 90b34c78-9204-4a2f-8c23-a0f8d5676b6d | public    | a90927be-72a4-47d1-8285-ba5bc403d99a             |
  | cdb1392e-b9a2-4d85-b736-a729235b4b82 | user-3net | 13a4c458-2c00-4da7-9f68-97b0d6a0a74b 10.1.2.0/24 |
  +--------------------------------------+-----------+--------------------------------------------------+
  stack@DVR-Controller:~/DEVSTACK/user-1$ neutron port-list --network-id cdb1392e-b9a2-4d85-b736-a729235b4b82 --device_owner 'network:dhcp'
  +--------------------------------------+------+-------------------+---------------------------------------------------------------------------------+
  | id                                   | name | mac_address       | fixed_ips                                                                       |
  +--------------------------------------+------+-------------------+---------------------------------------------------------------------------------+
  | ed9bf7f4-e5df-4543-ab9c-b9a7885fed68 |      | fa:16:3e:36:aa:1a | {"subnet_id": "13a4c458-2c00-4da7-9f68-97b0d6a0a74b", "ip_address": "10.1.2.3"} |
  +--------------------------------------+------+-------------------+---------------------------------------------------------------------------------+
  stack@Controller:~/DEVSTACK/user-1$
  stack@Controller:~/DEVSTACK/user-1$ cd ../manage
  stack@Controller:~/DEVSTACK/manage$ ./os_admin neutron dhcp-agent-list-hosting-net cdb1392e-b9a2-4d85-b736-a729235b4b82
  +--------------------------------------+------------+----------------+-------+
  | id                                   | host       | admin_state_up | alive |
  +--------------------------------------+------------+----------------+-------+
  | 674ffd44-f4a6-4695-b24c-59ef02d9cbd8 | Controller | True           | :-)   |
  +--------------------------------------+------------+----------------+-------+

  As an user of the tenant:

  stack@Controller:~/DEVSTACK/manage$ neutron port-delete ed9bf7f4-e5df-4543-ab9c-b9a7885fed68
  Deleted port: ed9bf7f4-e5df-4543-ab9c-b9a7885fed68

  stack@Controller:~/DEVSTACK/manage$ neutron port-list --network-id
  cdb1392e-b9a2-4d85-b736-a729235b4b82 --device_owner 'network:dhcp'

  stack@Controller:~/DEVSTACK/manage$

  
  The network is still scheduled with the same dhcp agent:
  stack@Controller:~/DEVSTACK/manage$ ./os_admin neutron dhcp-agent-list-hosting-net cdb1392e-b9a2-4d85-b736-a729235b4b82
  /home/stack/DEVSTACK/manage
  +--------------------------------------+------------+----------------+-------+
  | id                                   | host       | admin_state_up | alive |
  +--------------------------------------+------------+----------------+-------+
  | 674ffd44-f4a6-4695-b24c-59ef02d9cbd8 | Controller | True           | :-)   |
  +--------------------------------------+------------+----------------+-------+

  
  The port deletion should not be allowed.  This makes the configuration of the qdhcp namespace on the controller node inconsistent with the databse 

  information.  The tap device taped9bf7f4-e5 still in the namespace but
  the port is no longer found in the database.

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