evacuate/host-evacuate do not accept fqdn for target host
Bug #1278432 reported by
Vincent Untz
This bug report is a duplicate of:
Bug #1310340: live migration fails when use long hostname of a nova compute target host.
Edit
Remove
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
New
|
Undecided
|
Unassigned | ||
| python-novaclient |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Interestingly, if I run "nova evacuate" or "nova host-evacuate" with a FQDN for the target host, I end up with:
"Error while evacuating instance: Compute host $FQDN not found. (HTTP 404)"
However, in "nova hypervisor-list", I do get FQDNs. But it's true that in "nova service-list", I only have the short hostname (without the domain).
Revision history for this message
| Vincent Untz (vuntz) wrote | #1 |
Revision history for this message
| melanie witt (melwitt) wrote | #2 |
| Changed in python-novaclient: | |
| status: | New → Invalid |
To post a comment you must log in.
Arguably, it could be said that it's a bug on the server side, with nova that should accept hostnames as found in the list of hypervisors, not just hostnames as found in the list of services...
So maybe this should be moved to nova.