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/1321774
Title:
Wrong error when creating different instances with the same hostname
into the same DNS domain
Status in OpenStack Compute (nova):
Expired
Bug description:
The bug related to creating different instances with the same hostname
into the same DNS domain was reported on launchpad
(https://bugs.launchpad.net/nova/+bug/1283538) and is being solved
with its review (https://review.openstack.org/#/c/94252/).
However, the error is thrown when the instance is being built and it
says "Error: No valid host was found.". It should say something like
"Error: An instance already exists with the hostname <instance name>".
Internally, an error with message "The DNS entry %(name)s already
exists in domain %(domain)s." is being thrown, but it is not shown to
the caller interface, such as Horizon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1321774/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
