nova-manage vm list output is not consistent with nova cli - changes _ to - in name !
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Russell Bryant |
Bug Description
brebner@
+------
| ID | Name | Status | Networks |
+------
| 5963 | gavinmax_mx_inst_0 | ACTIVE | null=10.13.25.7, 15.184.92.97 |
| 5964 | gavinmax_mx_inst_1 | ACTIVE | null=10.13.25.6, 15.184.92.117 |
| 5965 | gavinmax_mx_inst_2 | ACTIVE | null=10.13.25.8, 15.184.92.118 |
| 5966 | test4 | ACTIVE | null=10.13.25.9, 15.184.92.119 |
+------
brebner@
however
nova-manage vm list | grep gavinmax
gavinmax-mx-inst-0 az1-nv-
gavinmax-mx-inst-1 az1-nv-
gavinmax-mx-inst-2 az1-nv-
test4 az1-nv-
[gavin@gbcsbu tests]$
The correct names are '_' not '-' so why is the nova-manage output changing them ?
Diablo-final based system
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in nova: | |
milestone: | essex-4 → none |
Changed in nova: | |
milestone: | none → essex-4 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-4 → 2012.1 |
Thanks for the report. This appears to be an intentional difference in behavior. There are two related bits of information associated with an instance, a "hostname" and "display name". What you get back from "nova list" is the display name. What you see from nova-manage is the hostname, which is a somewhat sanitized version of the display name.
It's fairly simple to adjust nova-manage to use the display name (patch attached). However, according to comments in review 3523 (https:/ /review. openstack. org/#change, 3523), nova-manage is going away, so it seems fruitless to make the change.
Hopefully this explanation at least makes it more clear why the results differ.