Coder Workspaces Stuck in Apply Complete
After updating to the latest 2.18.x release, we're seeing the following on coder workspaces (custom kubevirt template)
It looks like the terraform build completes, the terraform process exits inside coder, but coder still thinks the workspace is building. tried rolling back versions but still no fix. is this a known issue?
16 Replies
<#1336062330139840602>
Category
Bug report
Product
Coder (v2)
Platform
Linux
Logs
Please post any relevant logs/error messages.
hey @bl1tzcra1g, could you send a screenshot alongside with your template?
test
ok nice discord is back. we actually managed to figure it out. there were a number of old terraform outputs we were passing through so when we removed them it worked
my colleague said "coder doesn't take terraform outputs anymore, it crashes it". interesting that there was no output. happy to provide the previous template if that helps things on your end but otherwise this can be marked as solved. appreciate the follow up
that is weird, i'd like the old template to investigate on this!
also, it seems like you are using
local-exec, is this so you can keep the same VM object and just start it instead of recreating a new one every time?yeah exactly
it's an odd template, had to work around quite a few limitations with kubevirt and coder templates but it's been rock solid for a year+
I just stepped away from my computer but I'll send it as soon as I'm back
sorry completely forgot lol
no worries, could you also send a screenshot of the workspace page?
it seems to me that Coder might be waiting for the agent to connect
we have it fixed now but the workspace page was just stuck on the terraform output from above:
and never swapped to the screen with the agent/links to connect. we were able to confirm the agent was running via systemctl
weird, how have you fixed it?
this
sorry, i'm all over the place lol
thanks :)
is this template the fixed one or the one with the issue then?
all good haha, can imagine the context switching necessary for swapping b/w tickets and bug work.
it's the one with the issue
i can send the fixed one as well
yes please, i'll take a look to see if i can reproduce!
the fixed one should help find what was the issue
i'm resolving this issue but keeping it for later
@Phorcys closed the thread.