Description of problem:
Seen this just once, not able to find related bug or change in VDSM.
It seems that monitoring runs just before a merge finishes and sets the device threshold for extension to a value that is only valid for
the previous active volume. For the new active value the value does not make sense, but the value is enough to trigger an extension
event and VDSM pauses the VM, as the request makes no sense.
Version-Release number of selected component (if applicable):
Benny, can you please have a look?
Live merge flow changed in 4.4.6.
Closing this bug, please reopen if you encounter it again.