DBDuplicateEntry error, create-port on IPv6 subnet

Bug #1369590 reported by isador999
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
Expired
Medium
Unassigned

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.

Tags: ipv6
tags: added: ipv6
Changed in neutron:
importance: Undecided → Medium
assignee: nobody → Eugene Nikanorov (enikanorov)
Revision history for this message
Ann Taraday (akamyshnikova) wrote :

Create four networks with ipv4 and ipv6 subnets each, dhcp disabled on ipv6 subnets. For all ipv6 subnets ports are created without any 'Internal Server error'. Please, see http://paste.openstack.org/show/125761/. Please, provide more information may be step by step how such error appear and what plugins is used.

Changed in neutron:
status: New → Incomplete
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

This bug is > 172 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

Changed in neutron:
assignee: Eugene Nikanorov (enikanorov) → 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.