Confirmation of autoscaling runner behavior when spot instances are unavailable

Replace this template with your information

Describe your question in as much detail as possible:

The behavior I’ve observed is that when there is no autoscaling capacity in AWS for a particular instance type, an autoscaling runner will still request a job. This seems to be true even when I set IdleCount>0, which I thought might at least ensure that no jobs are accepted when there are no instances to run them.

  • What are you seeing, and how does that differ from what you expect to see?

The job will be assigned to a runner that cannot service it and will timeout eventually. I’d like jobs never to hang.

  • Consider including screenshots, error messages, and/or other helpful visuals

  • What version are you on? Are you using self-managed or

    • GitLab (Hint: /help): 15.1.0-pre
    • Runner (Hint: /admin/runners): 14.8.3
  • Add the CI configuration from .gitlab-ci.yml and other configuration if relevant (e.g. docker-compose.yml)

  • What troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?

As mentioned, I tried setting IdleCount>0 but it didn’t help.