Description of problem: This is the VDSM side of the bug - the domain should include in its metadata a flag that will tell VDSM to refuse to put this domain into maintenance. A separate bug will be for Engine to recognize this flag as well.
Is this part of the storage stabilization effort?
(In reply to Yaniv Lavi from comment #1) > Is this part of the storage stabilization effort? Yes.
One issue, who will be responsible for putting the domain in maintenance when this is actually needed? For example, you cannot upgrade sanlock if there is an active storage domain.
Hosted engine knows how to unmount it's domain and it can be done with 'hosted-engine --disconnect-storage' call. We don't need metadata, as everything can be done on the engine side.
*** This bug has been marked as a duplicate of bug 1445199 ***