yahoo-eng-team team mailing list archive

Thread
Date
[Bug 1968136] Re: If network:dhcp port is deleted, it will never be recreated

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Giuseppe Petralia <1968136@xxxxxxxxxxxxxxxxxx>
Date: Thu, 07 Apr 2022 08:00:46 -0000
Reply-to: Bug 1968136 <1968136@xxxxxxxxxxxxxxxxxx>
Sender: noreply@xxxxxxxxxxxxx
** Description changed:

  If dhcp port of a subnet is deleted, it will never be recreated.
  
  Versions:
  =========
  neutron: 2:16.4.0-0ubuntu3~cloud0
  ovn: 20.03.2-0ubuntu0.20.04.2~cloud0
  
  Steps to reproduce:
  ===================
  
  1. Network: dc4c5b7c-c749-4815-9feb-08afef46ab45
     Subnet: 1eeb158c-7d98-4d4a-8567-634cc63a00d3
     Dhcp is enabled
  
     port list shows the dhcp port:
  
  $ openstack port list --network dc4c5b7c-c749-4815-9feb-08afef46ab45 --long
  +--------------------------------------+------+-------------------+----------------------------------------------------------------------------+--------+-----------------+--------------+------+
  | ID                                   | Name | MAC Address       | Fixed IP Addresses                                                         | Status | Security Groups | Device Owner | Tags |
  +--------------------------------------+------+-------------------+----------------------------------------------------------------------------+--------+-----------------+--------------+------+
  | 3d58eaae-d9be-4618-9427-8d4e5a402530 |      | fa:16:3e:2e:ee:12 | ip_address='192.168.0.2', subnet_id='1eeb158c-7d98-4d4a-8567-634cc63a00d3' | DOWN   |                 | network:dhcp |      |
  +--------------------------------------+------+-------------------+----------------------------------------------------------------------------+--------+-----------------+--------------+------+
  
  2. Disable dhcp on subnet and remove the dhcp port
  
  $ openstack subnet set --no-dhcp 1eeb158c-7d98-4d4a-8567-634cc63a00d3
  $ openstack port delete 3d58eaae-d9be-4618-9427-8d4e5a402530
  
  3. Enable dhcp on subnet
  $ openstack subnet set --dhcp 1eeb158c-7d98-4d4a-8567-634cc63a00d3
  
  Expected Result
  ===============
  Dhcp port is recreated
  
  Actual Result
  =============
  Dhcp port is not created
  
  Workaround
  ==========
+ 
  Create manually the dhcp port:
  
- $ openstack port create --mac-address fa:16:3e:18:8b:1f --network
- 4dc4c5b7c-c749-4815-9feb-08afef46ab45 --device-owner network:dhcp
- --fixed-ip subnet=1eeb158c-7d98-4d4a-8567-634cc63a00d3,ip-
- address=192.168.0.2 dhcp-port
+ $ openstack port create --network 4dc4c5b7c-c749-4815-9feb-08afef46ab45
+ --device-owner network:dhcp --no-fixed-ip dhcp-port
+ 
+ Toggle dhcp on subnet 1eeb158c-7d98-4d4a-8567-634cc63a00d3 so that an IP
+ will be assigned to the dhcp port

** Also 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/1968136

Title:
  If network:dhcp port is deleted, it will never be recreated

Status in networking-ovn:
  New
Status in neutron:
  New

Bug description:
  If dhcp port of a subnet is deleted, it will never be recreated.

  Versions:
  =========
  neutron: 2:16.4.0-0ubuntu3~cloud0
  ovn: 20.03.2-0ubuntu0.20.04.2~cloud0

  Steps to reproduce:
  ===================

  1. Network: dc4c5b7c-c749-4815-9feb-08afef46ab45
     Subnet: 1eeb158c-7d98-4d4a-8567-634cc63a00d3
     Dhcp is enabled

     port list shows the dhcp port:

  $ openstack port list --network dc4c5b7c-c749-4815-9feb-08afef46ab45 --long
  +--------------------------------------+------+-------------------+----------------------------------------------------------------------------+--------+-----------------+--------------+------+
  | ID                                   | Name | MAC Address       | Fixed IP Addresses                                                         | Status | Security Groups | Device Owner | Tags |
  +--------------------------------------+------+-------------------+----------------------------------------------------------------------------+--------+-----------------+--------------+------+
  | 3d58eaae-d9be-4618-9427-8d4e5a402530 |      | fa:16:3e:2e:ee:12 | ip_address='192.168.0.2', subnet_id='1eeb158c-7d98-4d4a-8567-634cc63a00d3' | DOWN   |                 | network:dhcp |      |
  +--------------------------------------+------+-------------------+----------------------------------------------------------------------------+--------+-----------------+--------------+------+

  2. Disable dhcp on subnet and remove the dhcp port

  $ openstack subnet set --no-dhcp 1eeb158c-7d98-4d4a-8567-634cc63a00d3
  $ openstack port delete 3d58eaae-d9be-4618-9427-8d4e5a402530

  3. Enable dhcp on subnet
  $ openstack subnet set --dhcp 1eeb158c-7d98-4d4a-8567-634cc63a00d3

  Expected Result
  ===============
  Dhcp port is recreated

  Actual Result
  =============
  Dhcp port is not created

  Workaround
  ==========

  Create manually the dhcp port:

  $ openstack port create --network
  4dc4c5b7c-c749-4815-9feb-08afef46ab45 --device-owner network:dhcp
  --no-fixed-ip dhcp-port

  Toggle dhcp on subnet 1eeb158c-7d98-4d4a-8567-634cc63a00d3 so that an
  IP will be assigned to the dhcp port

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-ovn/+bug/1968136/+subscriptions