401 error for requests to coder.example.com after "Update" option following template change
- 主要语言
- Go
- 星标
- 300
- 派生
- 64
- 平均合并
- 20 分钟
- 30 天内合并 PR
- 1
描述
I am seeing an issue where when I use the "Update" option in the coder dashboard after a template change, the coder process get stuck in this state, where it gets 401 errors trying to talk to the coder agent URL. The issue is resolved by using the "Restart" option instead.
```
2024-06-12 19:43:20.920 [info] connecting to coderd
2024-06-12 19:43:20.934 [warn] run exited with error ...
error= GET https://coder.example.com/api/v2/workspaceagents/me/rpc?version=2.1: unexpected status code 401: unexpected non-JSON response "": Try logging in using 'coder login'.
Error: no response body
```
I am using "token" authentication with the coder agent, with config passed to the container for the auth as:
```
{
name = "CODER_AGENT_TOKEN"
value = try(coder_agent.main[0].token, "")
},
{
name = "CODER_AGENT_URL"
value = data.coder_workspace.me.access_url
},
```
This issue does away after doing a "restart" of the instance.
Discord discussion here: https://discord.com/channels/747933592273027093/1250538421789790271/1250538421789790271
贡献指南
这个仓库没有索引到贡献指南
调研方向
未指定 repository 文件或测试。使用 token 身份验证复现一次模板更改,然后执行 dashboard 的 Update 选项,将其与 Restart 进行比较,并检查 agent 和 coderd 日志;当 Update 在没有 401 错误的情况下重新连接时,即表示完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- docker, go
- 领域
- authentication, devops
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 25/100