Description of problem:
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