4 May
2016
4 May
'16
1:34 p.m.
Bill James <bill.james@j2.com> writes:
.recovery setting before removing: p298 sS'status' p299 S'Paused' p300
After removing .recovery file and shutdown and restart: V0 sS'status' p51 S'Up' p52
Thank you for the information. I was able to reproduce the problem with mistakenly reported paused state when Vdsm receives unexpected data from libvirt. I'll try to look at it. Restarting Vdsm (4.17.18 and some newer versions) afterwards remedies the problem for me, even without removing the recovery file. Milan