Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MGMT-12552: Day-2 agent stuck with status_info rebooting although the node is already part of the cluster #4610

Merged
merged 1 commit into from
Nov 15, 2022
Merged

MGMT-12552: Day-2 agent stuck with status_info rebooting although the node is already part of the cluster #4610

merged 1 commit into from
Nov 15, 2022

Commits on Nov 13, 2022

  1. MGMT-12552: Day-2 agent stuck with status_info rebooting although the… 

    … node is already part of the cluster

The following applies to kube-API only
The host UpdateInstallProgress will not update day-2 hosts to HostStatusAddedToExistingCluster if the host stage is Rebooting.
The host UpdateInstallProgress will update day-2 hosts to HostStatusAddedToExistingCluster if the host stage is Done
The agent controller will keep updateing day-2 agents if the agent stage is Rebooting, Configuring or Joined.
    @eranco74
    eranco74 committed Nov 13, 2022
    Configuration menu
    Copy the full SHA
    ecec245 View commit details
    Browse the repository at this point in the history