Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1117656

Summary: upload-to-image process stops when restarting Openstack services
Product: Red Hat OpenStack Reporter: Yogev Rabl <yrabl>
Component: openstack-cinderAssignee: Eric Harney <eharney>
Status: CLOSED UPSTREAM QA Contact: Dafna Ron <dron>
Severity: high Docs Contact:
Priority: high    
Version: 5.0 (RHEL 7)CC: eglynn, eharney, fpercoco, scohen, sgotliv, yeylon, yrabl
Target Milestone: ---   
Target Release: 6.0 (Juno)   
Hardware: x86_64   
OS: Linux   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-26 18:37:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yogev Rabl 2014-07-09 07:30:46 UTC
Description of problem:
I've started a process of upload a volume from Cinder to an image in Glance with the command:
# cinder upload-to-image ... 
Then in the middle of the process the I've restarted the Openstacks services. 
Both the volume in Cinder and the image create in Glance are stuck in status of "uploading" and "saving". 
but the process itself has halted.

Version-Release number of selected component (if applicable):
python-glanceclient-0.12.0-1.el7ost.noarch
python-glance-2014.1-4.el7ost.noarch
python-cinder-2014.1-7.el7ost.noarch
openstack-cinder-2014.1-7.el7ost.noarch
python-cinderclient-1.0.9-1.el7ost.noarch
openstack-glance-2014.1-4.el7ost.noarch


How reproducible:
100%

Steps to Reproduce:
1. Run the command:
# cinder upload-to-image <volume-id> --container-format bare --disk-format raw <image name>
2. Run the command:
# openstack-service restart  
3. check whether the image is been saved in the store.

Actual results:
the image-upload process is stuck and both volume and image statuses are "uploading" and "save".

Expected results:
The process should restart itself from the beginning or continue from the place it has stopped. 

Additional info:

Comment 2 Flavio Percoco 2014-07-09 07:47:25 UTC
I don't think this will be possible in the near future, not even if using taskflow and keeping the status of the task. The reason being that there's no support for re-startable uploads in Glance. We're currently working on 're-startable' downloads for it.

To be honest, although this may seem useful for users that have no control on the server, I don't really think it makes a whole lot of sense to support this feature.

Something that may indeed be a problem is the state the volume is left in when this happens. The immediate solution here is to delete the image, reset the volume status and start the process again.

Comment 3 Yogev Rabl 2014-07-13 11:59:33 UTC
I think the solution that you have proposed is very reasonable, as long as there are messages in both logs and UI that announce that the process has been restarted.

Comment 5 Red Hat Bugzilla 2023-09-14 02:11:16 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days