It should not be. Was there anything in the log? Storage failure or something?

Best regards

Martin Sivak

On Thu, Jun 14, 2018 at 11:59 AM, Callum Smith <[email protected]> wrote:
> So the one host with the stale-data, putting that into maintenance and then
> rebooting seems to have brought it back and stopped the errors. It seems the
> ha-broker is a bit more temperamental than usual after the 4.2.3.1 release.
>
> Regards,
> Callum
>
> --
>
> Callum Smith
> Research Computing Core
> Wellcome Trust Centre for Human Genetics
> University of Oxford
> e. [email protected]
>
> On 14 Jun 2018, at 10:34, Martin Sivak <[email protected]> wrote:
>
> 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 <[email protected]> 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. [email protected]
>
> On 14 Jun 2018, at 10:22, Martin Sivak <[email protected]> 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 <[email protected]> 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. [email protected]
>
> _______________________________________________
> Users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> 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/[email protected]/message/SR5RVQ2WFDMKNO4RXSCU45GJ7RTXDZX4/
>
>
>
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]/message/N552YEVKWL55CQJPJLTRZZMNBJY3KVMP/

Reply via email to