server create problems in boot-from-volume
Bug #1383338 reported by
Dean Troyer
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-openstackclient |
Fix Released
|
Medium
|
Dean Troyer |
Bug Description
A boot-from-volume via 'server create' has a couple of problems: --image is required; and the volume mapping must be an id not a name.
Changed in python-openstackclient: | |
status: | New → Triaged |
Changed in python-openstackclient: | |
assignee: | nobody → Dean Troyer (dtroyer) |
Changed in python-openstackclient: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I think the UI here needs to be rethought, it was copied from the nova command. --image is used to specify a Glance image, --volume should be used to specify a Cinder volume. The mapping is still required, maybe it can be inferred for the boot volume?