** Changed in: horizon/kilo
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1447288
Title:
create volume from snapshot using horizon error
Status in OpenStack Dashboard (Horizon):
Fix Released
Status in OpenStack Dashboard (Horizon) kilo series:
Fix Released
Bug description:
When I try to create a volume from snapshot using the OpenStack UI it
creates a new raw volume with correct size, but it's not created from
a snapshot.
$ cinder show 9d5d0ca1-3dd0-47b4-b9f4-86f97d65724e
+---------------------------------------+--------------------------------------+
| Property | Value
|
+---------------------------------------+--------------------------------------+
| attachments | []
|
| availability_zone | nova
|
| bootable | false
|
| consistencygroup_id | None
|
| created_at | 2015-04-22T18:08:53.000000
|
| description | None
|
| encrypted | False
|
| id |
9d5d0ca1-3dd0-47b4-b9f4-86f97d65724e |
| metadata | {}
|
| multiattach | False
|
| name | v2s2
|
| os-vol-host-attr:host | ubuntu@ns_nfs-1#nfs
|
| os-vol-mig-status-attr:migstat | None
|
| os-vol-mig-status-attr:name_id | None
|
| os-vol-tenant-attr:tenant_id | 4968203f183641b283e111a2f2d3333b
|
| os-volume-replication:driver_data | None
|
| os-volume-replication:extended_status | None
|
| replication_status | disabled
|
| size | 2
|
| snapshot_id | None
|
| source_volid | None
|
| status | available
|
| user_id | c8163c5313504306b40377a0775e9ffa
|
| volume_type | None
|
+---------------------------------------+--------------------------------------+
But when I use cinder command line everything seems to be fine.
$ cinder create --snapshot-id 382a0e1d-168b-4cf6-a9ff-715d8ad385eb 1
+---------------------------------------+--------------------------------------+
| Property | Value
|
+---------------------------------------+--------------------------------------+
| attachments | []
|
| availability_zone | nova
|
| bootable | false
|
| consistencygroup_id | None
|
| created_at | 2015-04-22T18:15:08.000000
|
| description | None
|
| encrypted | False
|
| id |
b33ec1ef-9d29-4231-8d15-8cf22ca3c502 |
| metadata | {}
|
| multiattach | False
|
| name | None
|
| os-vol-host-attr:host | ubuntu@ns_nfs-1#nfs
|
| os-vol-mig-status-attr:migstat | None
|
| os-vol-mig-status-attr:name_id | None
|
| os-vol-tenant-attr:tenant_id | 4968203f183641b283e111a2f2d3333b
|
| os-volume-replication:driver_data | None
|
| os-volume-replication:extended_status | None
|
| replication_status | disabled
|
| size | 1
|
| snapshot_id |
382a0e1d-168b-4cf6-a9ff-715d8ad385eb |
| source_volid | None
|
| status | creating
|
| user_id | c8163c5313504306b40377a0775e9ffa
|
| volume_type | None
|
+---------------------------------------+--------------------------------------+
So it looks like it uses different flows via UI and via command line
for some reason.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1447288/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
