yahoo-eng-team team mailing list archive

[isador999 <jeanbapt37@xxxxxxxxxx>]

Public bug reported:

Hi,

We have four Openstack networks, each with two subnets (IPv4 / IPv6). 
DHCPv6 is disabled on all IPv6 subnets. 

Only on Net1 and Net2, we have a problem with  :  'neutron port-create NETID1 --name MYPORT --fixed-ip SUBNET_IPv6_ID' 
It returns  :   'Internal Server error'  

and /var/log/neutron/server.log returns  :  
 raise exception.DBDuplicateEntry(columns, integrity_error)
2014-09-15 08:10:57.359 50254 TRACE neutron.api.v2.resource DBDuplicateEntry: (IntegrityError) (1062, "Duplicate entry 'fd00:21:1::44-eccdf9d7-1278-4eb8-9747-7485fb2466db-868967b4-ce73' for key 'PRIMARY'") 'INSERT INTO ipallocations (port_id, ip_address, subnet_id, network_id) VALUES (%s, %s, %s, %s)' (('669c81b5-5f1c-4beb-88f7-61c0d5e8d772', '21.1.0.51', '8220d8ff-fe10-4137-bff7-ff2ea7270f13', '868967b4-ce73-4a88-8bfe-5c6c8f90a50d'), ('669c81b5-5f1c-4beb-88f7-61c0d5e8d772', 'fd00:21:1::44', 'eccdf9d7-1278-4eb8-9747-7485fb2466db', '868967b4-ce73-4a88-8bfe-5c6c8f90a50d'))

We can delete this IPv6 address from the database, but this IPv6 address
is already used by an instance  !

So, I don't know if Dnsmasq or neutron-dhcp-agent is the root cause, but we can see Openstack don't choose a different IPv6 address for each port...  
Strangely, subnets on other networks (Net3, Net4) works perfectly.

** 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/1369590

Title:
  DBDuplicateEntry error,  create-port on IPv6 subnet

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Hi,

  We have four Openstack networks, each with two subnets (IPv4 / IPv6). 
  DHCPv6 is disabled on all IPv6 subnets. 

  Only on Net1 and Net2, we have a problem with  :  'neutron port-create NETID1 --name MYPORT --fixed-ip SUBNET_IPv6_ID' 
  It returns  :   'Internal Server error'  

  and /var/log/neutron/server.log returns  :  
   raise exception.DBDuplicateEntry(columns, integrity_error)
  2014-09-15 08:10:57.359 50254 TRACE neutron.api.v2.resource DBDuplicateEntry: (IntegrityError) (1062, "Duplicate entry 'fd00:21:1::44-eccdf9d7-1278-4eb8-9747-7485fb2466db-868967b4-ce73' for key 'PRIMARY'") 'INSERT INTO ipallocations (port_id, ip_address, subnet_id, network_id) VALUES (%s, %s, %s, %s)' (('669c81b5-5f1c-4beb-88f7-61c0d5e8d772', '21.1.0.51', '8220d8ff-fe10-4137-bff7-ff2ea7270f13', '868967b4-ce73-4a88-8bfe-5c6c8f90a50d'), ('669c81b5-5f1c-4beb-88f7-61c0d5e8d772', 'fd00:21:1::44', 'eccdf9d7-1278-4eb8-9747-7485fb2466db', '868967b4-ce73-4a88-8bfe-5c6c8f90a50d'))

  We can delete this IPv6 address from the database, but this IPv6
  address is already used by an instance  !

  So, I don't know if Dnsmasq or neutron-dhcp-agent is the root cause, but we can see Openstack don't choose a different IPv6 address for each port...  
  Strangely, subnets on other networks (Net3, Net4) works perfectly.

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