Bug 1054268

Summary: cinder: Task reporting mechanism
Product: Red Hat OpenStack Reporter: Dafna Ron <dron>
Component: openstack-cinderAssignee: Eric Harney <eharney>
Status: CLOSED UPSTREAM QA Contact: nlevinki <nlevinki>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.0CC: eharney, markmc, scohen, sgordon, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://blueprints.launchpad.net/cinder/+spec/task-reporting
Whiteboard: storage upstream_milestone_none upstream_status_unknown upstream_definition_obsolete
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-05-28 14:00:42 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:

Description Dafna Ron 2014-01-16 14:42:15 UTC
Description of problem:


https://blueprints.launchpad.net/cinder/+spec/task-reporting


currently the failure of a task will appear as a change in the volume status (example is this bug: 1254721).
even if a task has failed in pre-run, the volume status will be change to failure as a reporting tool for task status.
I suggest that we either need to to create a task mechanism or change the way tasks are handled in the db so that a task will not effect the status of a volume but will be their own status and be reported back to the user as a start/run/fail/succeed status.
this will free the error status of a volume for the cases where the volume is actually damaged or suspected as such.


Version-Release number of selected component (if applicable):


Please look at bug: 1034251