Ask Your Question
0

DuplicateRecord when assigning floating IP

asked 2019-05-05 06:12:54 -0500

ephracis gravatar image

I have created a zone in Designate like this:

openstack zone create --email "mail@test.example.com" test.example.com.

I have then created a Heat stack with a router and a network. The network has test.example.com set as the DNS domain.

I create an instance on and attach to the network. When I assign a floating IP I get an error:

Unable to associate floating IP 10.51.0.27 to fixed IP 192.168.0.11 for instance 4c82477e-5281-499c-8919-c2a62fc9a1e0. 
Error: Request Failed: internal server error while processing your request.
Neutron server returns request_ids: ['req-59fc2242-a59a-4bcf-8cef-9af3e0119da3']

But when I check the instance it has a floating IP assigned and I can reach it properly.

When I check the logs for neutron I see this:

update failed: No details.: Conflict: Duplicate RecordSet

Any ideas on what I might have done wrong, or how to further troubleshoot this?

edit retag flag offensive close merge delete

Comments

While I don’t know that much about Designate, I would check Designate logs and also inspect the DNS record(s) that Designate created.

Bernd Bausch gravatar imageBernd Bausch ( 2019-05-05 06:52:25 -0500 )edit

Designate contains the same error: Duplicate RecordSet. No other clues unfortunately.

ephracis gravatar imageephracis ( 2019-05-09 19:12:35 -0500 )edit

1 answer

Sort by » oldest newest most voted
0

answered 2019-05-05 18:22:56 -0500

grahamhayes gravatar image

The first thing to check is what recordsets are already in use -

openstack recordset list all --all-projects

as an admin user should list all recordsets on the system - there may be a RecordSet left over.

the system will be trying to create a $SERVER_NAME.test.example.com recordset on floating IP creation.

edit flag offensive delete link more

Comments

Before I start there is no such recordset. When I run Vagrant and it assigns the floating IP it gets the error and afterward I see a single recordset. As I said, the floating IP is properly assigned to the instance and I can reach the instance on the hostname pointing to the floating IP.

ephracis gravatar imageephracis ( 2019-05-09 19:11:58 -0500 )edit

It works when I do not create my own zone but use the default zone instead (created in admin project by admin user and configured in designate as the default zone for both nova and neutron).

ephracis gravatar imageephracis ( 2019-05-09 19:42:39 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2019-05-05 06:12:54 -0500

Seen: 63 times

Last updated: May 05