yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

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


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

** Changed in: nova
       Status: Confirmed => Expired

-- 
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):
  Expired

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