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
This isn't a question or user support case (For Q&A and community support, go to Discussions).
I've read the Changelog before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes
To Reproduce
Make a workflow where one of the jobs uses an image that does not exist (such as `ghcr.io/actions/totally-fake-container:1`)
Describe the bug
The workflow gets stuck at "Initializing containers" and does not exit, and the cancel button on the UI does not work. I have to use the REST API's "secret" force-cancel endpoint to stop the workflow.
Describe the expected behavior
The action would fail as soon as it couldn't pull the image
The workflow and runner provisioning are completely distinct actions. The scale set in response to a workflow tries to provision runners that will potentially execute the job. The runner is not tied to the workflow it is provisioned for.
For example, if you have min-runners of 1, and 1 workflow is scheduled, then the available runner will pick it up. This is intended behavior. If you fix the image and install the scale set, it should be able to pick up where it left off and execute your workflow.
Closing this issue, but feel free to comment on it 🙂
Checks
Controller Version
0.9.3
Deployment Method
Helm
Checks
To Reproduce
Describe the bug
The workflow gets stuck at "Initializing containers" and does not exit, and the cancel button on the UI does not work. I have to use the REST API's "secret" force-cancel endpoint to stop the workflow.
Describe the expected behavior
The action would fail as soon as it couldn't pull the image
Additional Context
Controller Logs
Runner Pod Logs
The text was updated successfully, but these errors were encountered: