Dear Callum,
unknown stale-data means the hosts did not submit status update during
the last minute. That might be just a glitch or something happened to
the storage connection there.
Best regards
Martin Sivak
On Thu, Jun 14, 2018 at 11:28 AM, Callum Smith <
callum@well.ox.ac.uk> wrote:
Dear Martin,
The engine is running happily and migration appears to work although it
appears one node has dropped into "unknown stale-data" on vm-status (the
node that is neither the originator or the target for the migration.
Regards,
Callum
--
Callum Smith
Research Computing Core
Wellcome Trust Centre for Human Genetics
University of Oxford
e. callum@well.ox.ac.uk
On 14 Jun 2018, at 10:22, Martin Sivak <msivak@redhat.com> wrote:
Hi,
is the engine running even though you see the errors in the log?
Hosted engine agents fight for the lock when starting the engine VM.
One wins and the others report an issue. We have some checks in place
to silence those, but maybe it leaked again.
This might be just annoying as long as the engine is up. Manually
clicking the migrate button should also work.
Best regards
Martin Sivak
On Thu, Jun 14, 2018 at 10:41 AM, Callum Smith <callum@well.ox.ac.uk> wrote:
Dear All,
Getting an issue where the HE can't b migrated, the log is full of:
"VM HostedEngine is down with error. Exit message: resource busy: Failed to
acquire lock: Lease is held by another host."
engine.log attached
Regards,
Callum
--
Callum Smith
Research Computing Core
Wellcome Trust Centre for Human Genetics
University of Oxford
e. callum@well.ox.ac.uk
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/SR5RVQ2WFDMKNO4RXSCU45GJ7RTXDZX4/