You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.
After a rolling update, job offers were not sent out when one of the machines went down. list-units still showed an old machine running the units. The etcd cluster was not affected by this update other than a leader election.
Starting and stopping the units fixed the problem.
The text was updated successfully, but these errors were encountered:
When the one machine rebooted, it should have caused a MachineRemoved event to go out to the rest of the cluster. One of those other machines should have responded accordingly by cleaning up that now-removed machine's artifacts from the cluster (including the defunct job states).
I'm not sure why this didn't happen, but it could have been due to a race with the leader election.
After a rolling update, job offers were not sent out when one of the machines went down.
list-units
still showed an old machine running the units. The etcd cluster was not affected by this update other than a leader election.Starting and stopping the units fixed the problem.
The text was updated successfully, but these errors were encountered: