multinic is incompatible with instance DNS manager

[Mark McLoughlin]

I'm not terribly familiar with this stuff, but playing around with the test_add_fixed_ip() multinic test in test_api_samples, I was getting:

   "The DNS entry new-server-test already exists in domain"

If you look at allocate_fixed_ip() in NetworkManager, this stands out:

            if self._validate_instance_zone_for_dns_domain(context, instance):
                self.instance_dns_manager.create_entry(
                    name, address, "A", self.instance_dns_domain)

How can it make sense to allocate the same DNS entry every fixed IP address allocated to an instance?

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/42435

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/42435
Committed: http://github.com/openstack/nova/commit/454dce8271cb34f187ea680e50366cecc3bbfde7
Submitter: Jenkins
Branch: master

commit 454dce8271cb34f187ea680e50366cecc3bbfde7
Author: Mark McLoughlin <email address hidden>
Date: Fri Aug 16 22:28:44 2013 +0100

    Fix remove_fixed_ip test with CastAsCall

    If you enable CastAsCall, a bunch of issues with the remove_fixed_ip
    API sample integration test crops up.

    Firstly, the sample network is getting created with 'fake-mini' from
    CONF.host as the network host rather than the host UUID generated for
    the network service in start_service(). This results in
    allocate_fixed_ip() attempting to invoke an RPC on a non-existant host.

    Secondly, the test is attempting to remove a fixed IP which was never
    allocated. Use the add_fixed_ip() test to allocate a fixed IP and then
    remove that one, which is 10.0.0.3 rather than 10.0.0.2 which is the
    IP reserved for VPN.

    Lastly, disable the instance DNS manager because it seems this isn't
    compatible with multinic. I was getting FloatingIpDNSExists raised.

    blueprint: oslo-messaging
    Related-Bug: #1213251
    Change-Id: I9854863bbec8834c638c55832411f63da570f82d

[Mark McLoughlin (markmc)]

The above commit was not a fix - it disabled the use of DNS manager in the multinic test

[Sean Dague (sdague)]

The bug doesn't provide the solution to fixing, moving to Confirmed

[Markus Zoeller (markus_z) (mzoeller)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY