Description of problem: As part of Using CopyDataDivEndpoint to maintain jobs in VDSM, if a failure occurs, the volume will become illegal based on the infrastructure behavior. Some of the operations does not need to make the volume to be illegal on a failure like amend (or sparsify?) One possible solution is to add a flag that will indicate if the volume should become illegal on failure or not. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I discussed this with Adam, and we agreed that: - Operation on illegal volumes are ok, can use now set_illegal=False - Atomic operations on volume metadata are ok, can use new set_illegal=False - Any other operation on volume data or qcow2 metadata must set the volume to illegal before the operation and the volume should remain illegal if the operation failed.
This bug will be the infrastructure gap to support setting if a volume is illegal or not on failure. Every operation that was dependent on the CopyDataDivEndpoint and need to change the behavior will be followed by a dependent bug