yahoo-eng-team team mailing list archive

[Miguel Lavalle <miguel@xxxxxxxxxxxx>]

@Imran

This is the expected behavior. When publishing a floating ip in
Designate, its dns_name / dns_domain pair can come from 2 sources:

1) The dns_name / dns_domain attributes assigned to the floating ip when
it was created. In this case, the attributes are published in Designate
when the floating ip is created. Also, these attributes have precedence
over the alternative explained in point 2.

2) If the floating ip was created without its own dns_name / dns_domain
attributes, then it will adopt those of the port / network it is
associated with. In this case, the dns_name / dns_domain will be
published in Designate when the floating ip is associated to a port

So you are clearly using alternative 2. The error you are seeing is
really a consequence of the way Designate works: you are trying to
publish a duplicate name in a zone with the same record type (A). Let's
remove Neutron from the picture and try to add the same name twice with
the same record type (A) to the same zone using Designate directly. You
get an error: http://paste.openstack.org/show/584491/.

You have alternatives:

1) Create the VMs with different names
2) Assign different dns_domain to the networks
3) Keep the VMs and the networks with the same names / dns_domain, but assign different dns_name to the floating ips when you create them

** Changed in: neutron
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1628670

Title:
  Duplicate designate record error shown when floating ip attached to
  two VMs with same name

Status in neutron:
  Invalid

Bug description:
  We have observed this error in designate-neutron integration for
  mitaka.

   when we create a network and add a designate dns domain to it using
  "neutron net-update --dns-domain my-domain.com" , and later assign a
  floating IP, the designate record for floating IP gets created fine.

  However, when we create a second network, and add SAME designate
  domain like "neutron net-update __dns_domain my-domain.com", later
  create the VM with SAME name too, but this time the VM is created in
  this second network, upon floating IP association, we see this error
  in neutron logs:

  """

  /var/log/neutron/neutron-server.log:9698:2016-09-28 19:43:15.731 502 ERROR neutron.db.dns_db [req-4c6ff4f4-a542-49e2-8051-9e16404142c3 1de3aeb554644fccb20bbee5c9f41c9b e6fcd8295a5349e8bb96ec47c30b9cd7 - - -] Error publishing floating IP data in external DNS service. Name: 'nova-test'. Domain: 'my-domain.com.'. DNS service driver message 'Name nova-test is duplicated in the external DNS service'
  /var/log/neutron/neutron-server.log-9699-2016-09-28 19:43:15.731 502 ERROR neutron.db.dns_db Traceback (most recent call last):
  /var/log/neutron/neutron-server.log-9700-2016-09-28 19:43:15.731 502 ERROR neutron.db.dns_db   File "/usr/lib/python2.7/site-packages/neutron/db/dns_db.py", line 316, in _add_ips_to_external_dns_service
  /var/log/neutron/neutron-server.log-9701-2016-09-28 19:43:15.731 502 ERROR neutron.db.dns_db     records)
  /var/log/neutron/neutron-server.log-9702-2016-09-28 19:43:15.731 502 ERROR neutron.db.dns_db   File "/usr/lib/python2.7/site-packages/neutron/services/externaldns/drivers/designate/driver.py", line 142, in create_record_set
  /var/log/neutron/neutron-server.log-9703-2016-09-28 19:43:15.731 502 ERROR neutron.db.dns_db     raise dns.DuplicateRecordSet(dns_name=dns_name)
  /var/log/neutron/neutron-server.log:9704:2016-09-28 19:43:15.731 502 ERROR neutron.db.dns_db DuplicateRecordSet: Name nova-test is duplicated in the external DNS service
  /var/log/neutron/neutron-server.log-9705-2016-09-28 19:43:15.731 502 ERROR neutron.db.dns_db

  """

  is this because lack of multi-network support in designate neutron
  integration?

  the scenario is very simple, create two networks, update both networks
  with same dns designate domain, create two VMs with same name but in
  each separate network, when floating ip is associated to second vm ,
  we see duplicate record error

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