Restrating the compute service while taking snapshot of vm makes the snapshot stuck in saving state

Bug #991941 reported by Satya Sanjibani Routray
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Confirmed
Medium
Prateek Arora

Bug Description

Branch: diablo Stable

1. Create a vm and wait till active
2. Take a snapshot of vm
3 while taking snapshot restart the compute service of the node where the vm is created

Observation: snapshot stuck in saving state

expected: Snapshot should go to Error state or should come to active state

Tags: diablo
Revision history for this message
Mandar Vaze (mandarvaze) wrote :
Sean Dague (sdague)
tags: added: diablo
Changed in nova:
status: New → Confirmed
Revision history for this message
Thierry Carrez (ttx) wrote :

Lots of things were changed in that area in Essex. Any chancxe you could reproduce that on current or Essex ?

Changed in nova:
status: Confirmed → Incomplete
Revision history for this message
Thierry Carrez (ttx) wrote :

We cannot solve the issue you reported without more information. Could you please provide the requested information ?

Revision history for this message
Thierry Carrez (ttx) wrote :

This bug lacks the necessary information to effectively reproduce and fix it, therefore it has been closed. Feel free to reopen the bug by providing the requested information and set the bug status back to ''New''.

Changed in nova:
status: Incomplete → Invalid
Revision history for this message
Unmesh Gurjar (unmesh-gurjar) wrote :

I could reproduce the issue, due to a bug ( https://bugs.launchpad.net/nova/+bug/1075556) in snapshotting instance, which left the snapshot in 'queued' state. Also, after restarting the Compute service, the snapshot continues to stay in 'queued' state.

Therefore, resetting the bug status to New.

Changed in nova:
status: Invalid → New
Revision history for this message
Chuck Short (zulcss) wrote :

Changing status based on last comment.

Changed in nova:
importance: Undecided → Medium
status: New → Confirmed
Changed in nova:
milestone: none → grizzly-rc1
status: Confirmed → Triaged
Revision history for this message
Russell Bryant (russellb) wrote :

Since this is Medium priority and unassigned, I'm moving it off of the grizzly-rc1 blocker list and into the "nice to have for grizzly" list (tagged with grizzly-rc-potential).

tags: added: grizzly-rc-potential
Changed in nova:
milestone: grizzly-rc1 → none
Revision history for this message
Thierry Carrez (ttx) wrote :

Should probably be fied in the same run as bug 1143659 and bug 1064386...

Thierry Carrez (ttx)
tags: added: grizzly-backport-potential
removed: grizzly-rc-potential
Yang Yu (yuyangbj)
Changed in nova:
assignee: nobody → Yang Yu (yuyangbj)
description: updated
Alan Pevec (apevec)
tags: removed: grizzly-backport-potential
Changed in nova:
assignee: Yang Yu (yuyangbj) → nobody
Sean Dague (sdague)
Changed in nova:
status: Triaged → Confirmed
Changed in nova:
assignee: nobody → Pushkar Umaranikar (pushkar-umaranikar)
Revision history for this message
Pushkar Umaranikar (pushkar-umaranikar) wrote :
Changed in nova:
assignee: Pushkar Umaranikar (pushkar-umaranikar) → nobody
Prateek Arora (parora)
Changed in nova:
assignee: nobody → Prateek Arora (parora)
Revision history for this message
Prateek Arora (parora) wrote :

Isn't this bug a duplicate of 1064386?
https://bugs.launchpad.net/nova/+bug/1064386

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.