Creating a server with a name that already exists
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Dan Prince |
Bug Description
The 'Creating a server with a name that already exists is allowed' test case stopped working.
The source of the test case is here:
https:/
I did not found any documentation about the expected behaviour, but it changed.
I did not found any info how the "name" parameter in the post request will be used for DNS entry creation, or any info about the name must be unique.
In the
http://
"FloatingIpDNSE
The 2. server was created, but went into the error status around the DNS setting.
It occurred in the https:/
The issue seams reproducible.
If the unique name is required constrain, the request should fail on create,
otherwise it should be able to boot (ACTIVE status) the second instance.
Changed in nova: | |
assignee: | nobody → Dan Prince (dan-prince) |
status: | New → In Progress |
importance: | Undecided → High |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
milestone: | none → grizzly-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-2 → 2013.1 |
* both minidns and ldapdns do not allow duplicate hostnames.
* this problem cropped up since we enabled minidns for the builds, earlier dnsdriver was being used which did not any validation
Do we fix the test case? or is this a "feature" people depend on? Anyone know?