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 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
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
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 wrote:
> Dear Martin,
>
> The
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
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
5 matches
Mail list logo
