"The agent cannot authenticate until the workspace provision job has been completed."
I am trying to provision a Coder agent on a VM. I am doing this by creating a systemd unit that runs the Coder agent.
However, when the unit starts, as part of a remote exec provisioner, it just keeps repeating this:
Restarting the systemd unit has no effect.
The token is being passed through from the coder_agent resource (coder_agent.main.token).
With
I've tried adding a
I see an old closed issue https://github.com/coder/coder/issues/5704 as being similar, but there's no clear fix present there.
Perhaps worth mentioning:
- Using an AWS instance, but in a different account, so using token auth, not aws instance identity
- AWS instance is created by a module that is intended to work independently of Coder; seems to pose some issues for knitting the agent together with the instance, couldn't get
- Actual instance is spun up fine and seems happy except for the agent connection
However, when the unit starts, as part of a remote exec provisioner, it just keeps repeating this:
Restarting the systemd unit has no effect.
The token is being passed through from the coder_agent resource (coder_agent.main.token).
With
coder state pullI've tried adding a
coder_agent_instanceI see an old closed issue https://github.com/coder/coder/issues/5704 as being similar, but there's no clear fix present there.
Perhaps worth mentioning:
- Using an AWS instance, but in a different account, so using token auth, not aws instance identity
- AWS instance is created by a module that is intended to work independently of Coder; seems to pose some issues for knitting the agent together with the instance, couldn't get
coder_metadata- Actual instance is spun up fine and seems happy except for the agent connection
GitHub
I am using the vSphere plugin to clone virtual machines from templates on vSphere. After cloning, I used remote-exec provisioner and did an init of coder_agent and got the following error null_reso...
