yahoo-eng-team team mailing list archive

[Mark McLoughlin <markmc@xxxxxxxxxx>]

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

** Changed in: nova
       Status: Fix Committed => Won't Fix

** Changed in: nova
       Status: Won't Fix => Triaged

** Changed in: nova
   Importance: Undecided => Low

** Changed in: nova
     Assignee: Mark McLoughlin (markmc) => (unassigned)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1213251

Title:
  multinic is incompatible with instance DNS manager

Status in OpenStack Compute (Nova):
  Triaged

Bug description:
  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?

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