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 }}
Repository navigation
Agent fails to connect after updating existing running workspace to new template version #2970
I published a new version of our workspace template and then used coder update <WORKSPACE_NAME> from the CLI (also running v0.7.12) to update my existing workspace (the status of which was "running") to the new template version.
The agent never connects to the workspace. Checking the serial console of the EC2 instance in AWS console I see this error message repeated continously:
[ 568.940691] cloud-init[1363]: "error": GET <ELIDED>/api/v2/workspaceagents/me/listen: unexpected status code 403:
Agent trying to connect from non-latest build.
[ 568.941792] cloud-init[1363]: Error: build is outdated
Definition of Done
After some time, the agent in the workspace connects to the Coder server so that I can ssh to the workspace.
As a workaround, stopping and starting the workspace after updating the template gets the agent connected again, maybe because it causes a newer version of the agent to be downloaded to the workspace?
changed the title [-]Bug in v0.7.12 6f34cbf: Agent fails to connect after updating existing workspace to new template version[/-][+]Bug in v0.7.12 6f34cbf: Agent fails to connect after updating existing running workspace to new template version[/+]on Jul 13, 2022
changed the title [-]Bug in v0.7.12 6f34cbf: Agent fails to connect after updating existing running workspace to new template version[/-][+]Agent fails to connect after updating existing running workspace to new template version[/+]on Jul 18, 2022
This issue is becoming stale. In order to keep the tracker readable and actionable, I'm going close to this issue in 7 days if there isn't more activity.
Activity
kconley-sq commentedon Jul 13, 2022
As a workaround, stopping and starting the workspace after updating the template gets the agent connected again, maybe because it causes a newer version of the agent to be downloaded to the workspace?
[-]Bug in v0.7.12 6f34cbf: Agent fails to connect after updating existing workspace to new template version[/-][+]Bug in v0.7.12 6f34cbf: Agent fails to connect after updating existing running workspace to new template version[/+][-]Bug in v0.7.12 6f34cbf: Agent fails to connect after updating existing running workspace to new template version[/-][+]Agent fails to connect after updating existing running workspace to new template version[/+]github-actions commentedon Oct 16, 2022
This issue is becoming stale. In order to keep the tracker readable and actionable, I'm going close to this issue in 7 days if there isn't more activity.