<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary When a CI jobs variable in the rules block is a number and not a string, the job fails to be scheduled and shows an error message saying "The scheduler failed to assign job to the runner, please try again or contact system administrator" This seems to only happen for rule-variable and not for other ones (see example project). This happens on gitlab.com and on my own gitlab instance (14.0.2-ee onmibus install) ### Steps to reproduce 1. Create a gitlab.ci with the following content: <details><summary>Click to expand</summary> ``` variables: GLOBAL_VAR_AS_NUMBER: 5 foo: stage: build script: - echo ${GLOBAL_VAR_AS_NUMBER} bar: stage: build variables: JOBS_VAR_AS_NUMBER: 5 script: - echo ${JOBS_VAR_AS_NUMBER} baz: rules: - if: '$CI_COMMIT_REF_NAME == "main" && $CI_PIPELINE_SOURCE != "merge_request_event"' when: on_success variables: RULE_VAR_AS_NUMBER: 5 stage: build script: - echo ${RULE_VAR_AS_NUMBER} ``` </details> 2. Commit into main branch ### Example Project https://gitlab.com/AliGinBerlin/broken-ci-example Failed job: https://gitlab.com/AliGinBerlin/broken-ci-example/-/jobs/1397324829 ### What is the current *bug* behavior? Jobs `foo` and `bar` succeed, while job `baz` fails with two messages 1. "An error occurred while fetching the job log." error message on top 2. "The scheduler failed to assign job to the runner, please try again or contact system administrator" erro messqage where the logs would be. ### What is the expected *correct* behavior? The pipeline should succeed, or it should show that the gitlab-ci.yml is broken. I guess it is normal that variables should be strings, but on all other variable inputs it seems to accept numbers just fine. ### Relevant logs and/or screenshots   ### Output of checks This bug happens on GitLab.com and self hosted instances. #### Results of GitLab environment info <!-- Input any relevant GitLab environment information if needed. --> <details> <summary>Expand for output related to GitLab environment info</summary> <pre> System information System: Debian 10 Proxy: no Current User: git Using RVM: no Ruby Version: 2.7.2p137 Gem Version: 3.1.4 Bundler Version:2.1.4 Rake Version: 13.0.3 Redis Version: 6.0.14 Git Version: 2.32.0 Sidekiq Version:5.2.9 Go Version: unknown GitLab information Version: 14.0.2-ee Revision: 2504e045362 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 12.6 URL: https://gitlab.funny-farm-family.de HTTP Clone URL: https://gitlab.funny-farm-family.de/some-group/some-project.git SSH Clone URL: git@gitlab.funny-farm-family.de:some-group/some-project.git Elasticsearch: no Geo: no Using LDAP: no Using Omniauth: yes Omniauth Providers: GitLab Shell Version: 13.19.0 Repository storage paths: - default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git </pre> </details> #### Results of GitLab application Check <details> <summary>Expand for output related to the GitLab application check</summary> <pre> Checking GitLab subtasks ... Checking GitLab Shell ... GitLab Shell: ... GitLab Shell version >= 13.19.0 ? ... OK (13.19.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Internal API available: OK Redis available via internal API: OK gitlab-shell self-check successful Checking GitLab Shell ... Finished Checking Gitaly ... Gitaly: ... default ... OK Checking Gitaly ... Finished Checking Sidekiq ... Sidekiq: ... Running? ... yes Number of Sidekiq processes (cluster/worker) ... 1/1 Checking Sidekiq ... Finished Checking Incoming Email ... Incoming Email: ... Reply by email is disabled in config/gitlab.yml Checking Incoming Email ... Finished Checking LDAP ... LDAP: ... LDAP is disabled in config/gitlab.yml Checking LDAP ... Finished Checking GitLab App ... Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 6/2 ... yes 10/3 ... yes 10/4 ... yes 6/5 ... yes 6/6 ... yes 9/7 ... yes 2/8 ... yes Redis version >= 5.0.0? ... yes Ruby version >= 2.7.2 ? ... yes (2.7.2) Git version >= 2.31.0 ? ... yes (2.32.0) Git user has default SSH configuration? ... yes Active users: ... 3 Is authorized keys file accessible? ... yes GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... yes Elasticsearch version 7.x (6.4 - 6.x deprecated to be removed in 13.8)? ... skipped (elasticsearch is disabled) Checking GitLab App ... Finished Checking GitLab subtasks ... Finished </pre> </details> ### Possible fixes https://gitlab.com/AliGinBerlin/broken-ci-example/-/blob/main/.gitlab-ci.yml#L21