We recently had this bug[1]. The thought that came from it is the handling of error code after running virDomainSnapshotCreateXML, we encountered VIR_ERR_OPERATION_ABORTED(78).
Apparently, the new volume is in use. Are there cases where this will happen and the new volume won't appear in the volumes chain? Can we detect / know when?
Thinking aloud, if we can detect such cases we can prevent rolling back by reporting it back from VDSM to ovirt. Or, if it can't be detected to go on the safe side in order to save data corruption and prevent the rollback as well.
Currently, in ovirt, if the job is aborted, we will look into the chain to decide whether to rollback or not.
Regards,
Liran.
