Public bug reported:
Reproducing method as following:
1、Boot a vm from the image
2、Create a blank volume .
3、Attach the volume to the vm .
4、Snapshot the vm.
6、After the fourth step, you will find that you have a new image in glance.
We're supposed to call it “vm_snapshot_image”.
7、Boot a new vm from the "vm_snapshot_image", but the new vm's data volume
was lost.
** Affects: nova
Importance: Undecided
Assignee: YaoZheng_ZTE (zheng-yao1)
Status: New
** Description changed:
Reproducing method as following:
- 1、Boot a vm from the image
+ 1、Boot a vm from the image
2、Create a blank volume .
3、Attach the volume to the vm .
4、Snapshot the vm.
6、After the fourth step, you will find that you have a new image in glance.
- We're supposed to call it “vm_snapshot_image”.
- 7、Boot a new vm from the "vm_snapshot_image", but the new vm's data volume
was lost.
+ We're supposed to call it “vm_snapshot_image”.
+ 7、Boot a new vm from the "vm_snapshot_image", but the new vm's data volume
was lost.
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1563209
Title:
instance's snapshot image can't restore the instance
Status in OpenStack Compute (nova):
New
Bug description:
Reproducing method as following:
1、Boot a vm from the image
2、Create a blank volume .
3、Attach the volume to the vm .
4、Snapshot the vm.
6、After the fourth step, you will find that you have a new image in glance.
We're supposed to call it “vm_snapshot_image”.
7、Boot a new vm from the "vm_snapshot_image", but the new vm's data volume
was lost.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1563209/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
