Closed roblabla closed 11 months ago
That should be resolved once https://github.com/cirruslabs/orchard/pull/129 is merged.
Is there any way I can repair my cluster, or should I just nuke it? Because it looks impossible to delete the "broken" VM, even going through curl doesn't work:
$ curl -u <redacted> -X DELETE https://myorchardcluster/v1/vms/test%2froblabla
404 page not found
The reason seems to be that Gin unescapes the Path very early, and then tries to match its URL parameters on the already-unescaped path, unless some options are set (see https://github.com/gin-gonic/gin/blob/c2ba8f19ec19914b73290c53a32de479cd463555/gin.go#L126 )
I was trying to find some way to namespace VMs in my cluster, so I tried putting a
/
in the VM name. That led to some fun stuff - as the VM never started, and could not be deleted:The VM never spawned, because tart seems to not have liked the name with the slash in it, according to the worker log:
Furthermore, the worker failed to put the VM in the failed state when talking to the controller, again probably due to the slash in the name:
This failure to communicate with the controller then caused the worker to enter a crash loop: