DHCPv6 stateful doesn't assign IP to ports created before it

Bug #1365756 reported by Sagi (Sergey) Shnaidman
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Expired
Low
Unassigned

Bug Description

When we create port in network without subnets(*) and then create IPv4 subnet with DHCP enabled, the port gets IP automatically. Unlike so with IPv6 subnets. When we create subnet with DHCPv6 stateful the port doesn't get anything from DHCP server automatically, only after explicit port-update. It's inconsistence.

With IPv4:
$ neutron net-create netto
$ neutron port-create netto
$ neutron subnet-create --ip-version=4 netto "192.168.111.0/24"
$ neutron port-list | grep 9856ecc4-9fc0-495c-81d1-686502a3ec83 # Port ID

| cb1f0dad-d393-49fc-a3ed-098a7e1d3692 | | fa:16:3e:79:04:d6 | {"subnet_id": "9856ecc4-9fc0-495c-81d1-686502a3ec83", "ip_address": "192.168.111.2"} |

With IPv6:

$ neutron net-create netto6
Created a new network:
+---------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| admin_state_up | True |
| id | b3858d5e-4665-422a-8511-6dd79f54437f |
| name | netto6 |
| provider:network_type | vxlan |
| provider:physical_network | |
| provider:segmentation_id | 1005 |
| router:external | False |
| shared | False |
| status | ACTIVE |
| subnets | |
| tenant_id | b1be3cf4e956459cad6b3f6541bbbad8 |
+---------------------------+--------------------------------------+

$ neutron port-create netto6
Created a new port:
+-----------------------+--------------------------------------+
| Field | Value |
+-----------------------+--------------------------------------+
| admin_state_up | True |
| allowed_address_pairs | |
| binding:host_id | |
| binding:profile | {} |
| binding:vif_details | {} |
| binding:vif_type | unbound |
| binding:vnic_type | normal |
| device_id | |
| device_owner | |
| fixed_ips | |
| id | bd12d32c-66fc-4947-b266-c4d565454174 |
| mac_address | fa:16:3e:a2:d8:14 |
| name | |
| network_id | b3858d5e-4665-422a-8511-6dd79f54437f |
| security_groups | b2fdab5e-1aa1-49bd-9717-72b41b8d109e |
| status | DOWN |
| tenant_id | b1be3cf4e956459cad6b3f6541bbbad8 |
+-----------------------+--------------------------------------+

$ neutron subnet-create --ipv6-ra-mode=dhcpv6-stateful --ipv6-address-mode=dhcpv6-stateful --ip-version=6 netto6 "2002::/64"
Created a new subnet:
+-------------------+----------------------------------------------------------+
| Field | Value |
+-------------------+----------------------------------------------------------+
| allocation_pools | {"start": "2002::2", "end": "2002::ffff:ffff:ffff:fffe"} |
| cidr | 2002::/64 |
| dns_nameservers | |
| enable_dhcp | True |
| gateway_ip | 2002::1 |
| host_routes | |
| id | 66e3e3c6-d561-494a-aec7-4fee272cf71d |
| ip_version | 6 |
| ipv6_address_mode | dhcpv6-stateful |
| ipv6_ra_mode | dhcpv6-stateful |
| name | |
| network_id | b3858d5e-4665-422a-8511-6dd79f54437f |
| tenant_id | b1be3cf4e956459cad6b3f6541bbbad8 |
+-------------------+----------------------------------------------------------+

$ neutron port-list | grep bd12d32c-66fc-4947-b266-c4d565454174 # Port ID

| bd12d32c-66fc-4947-b266-c4d565454174 | | fa:16:3e:a2:d8:14 |

The same thing also with :
1) --ipv6-ra-mode=dhcpv6-stateless --ipv6-address-mode=dhcpv6-stateless
2) --ipv6-address-mode=dhcpv6-stateful only
3) --ipv6-address-mode=dhcpv6-stateless only

-------
(*) why to do it? is it real user story?

Tags: api ipv6
description: updated
description: updated
tags: added: api
Changed in neutron:
importance: Undecided → Low
Revision history for this message
Xu Han Peng (xuhanp) wrote :
Download full text (4.3 KiB)

I followed the IPv4 instructions described in this problem but I cannot see the fixed_ip assigned:

# neutron net-create netto
Created a new network:
+---------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| admin_state_up | True |
| id | b8f3095c-8b69-486a-8ec8-7559298440ef |
| name | netto |
| provider:network_type | local |
| provider:physical_network | |
| provider:segmentation_id | |
| router:external | False |
| shared | False |
| status | ACTIVE |
| subnets | |
| tenant_id | 3a7fb324b20545458c2997ac7720b4b7 |
+---------------------------+--------------------------------------+

# neutron port-create netto
Created a new port:
+-----------------------+--------------------------------------+
| Field | Value |
+-----------------------+--------------------------------------+
| admin_state_up | True |
| allowed_address_pairs | |
| binding:host_id | |
| binding:profile | {} |
| binding:vif_details | {} |
| binding:vif_type | unbound |
| binding:vnic_type | normal |
| device_id | |
| device_owner | |
| fixed_ips | |
| id | 29c1f561-cdb8-4cd9-b553-92426c8fcb6f |
| mac_address | fa:16:3e:63:a6:90 |
| name | |
| network_id | b8f3095c-8b69-486a-8ec8-7559298440ef |
| security_groups | a0b40447-ed81-4d48-9e63-6abf44ea1976 |
| status | DOWN |
| tenant_id | 3a7fb324b20545458c2997ac7720b4b7 |
+-----------------------+--------------------------------------+

# neutron subnet-create --ip-version=4 netto "192.168.111.0/24"
Created a new subnet:
+-------------------+------------------------------------------------------+
| Field | Value |
+-------------------+------------------------------------------------------+
| allocation_pools | {"start": "192.168.111.2", "end": "192.168.111.254"} |
| cidr | 192.168.111.0/24 |
| dns_nameservers | |
| enable_dhcp | True ...

Read more...

Revision history for this message
Sagi (Sergey) Shnaidman (sshnaidm) wrote :

I can reproduce it again and again. Actually I agree with you, but I think this is should be the same behavior (whatever it will be) in both IPv4 and IPv6 versions.

MANJUNATH PATIL (mpatil)
Changed in neutron:
assignee: nobody → MANJUNATH PATIL (mpatil)
MANJUNATH PATIL (mpatil)
Changed in neutron:
assignee: MANJUNATH PATIL (mpatil) → nobody
Changed in neutron:
assignee: nobody → Aniruddha Singh Gautam (aniruddha-gautam)
Revision history for this message
Kannan Raman (rkannan-x) wrote :

HI Sergey Shnaidman,

Based on my investigation , This is not an actual Bug and misconfiguration of IPv6 firewall tables

You need to check with your IP6tables then you should get it

I gone through your configuration and tried out myself .

I have not seen any issue on that and working fine

Also i got the proper IPv6 address

[root@openstack-aio sysctl.d(keystone_admin)]# neutron port-list | grep ba7da800-1902-44b3-9fd1-995c8fc4d892
| ba7da800-1902-44b3-9fd1-995c8fc4d892 | | fa:16:3e:ef:83:69 | {"subnet_id": "15e3c69f-c7a0-4ead-8fc4-08cb2eece077", "ip_address": "11::2"}

Any clarification let me know

Revision history for this message
Sean M. Collins (scollins) wrote :

This bug is very old and has seen no activity in quite a while - setting to incomplete to reflect.

Changed in neutron:
status: New → Incomplete
assignee: Aniruddha Singh Gautam (aniruddha-gautam) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.