Undefined error with dynamic pipeline creation following upgrade of self hosted Gitlab to 17.3.1

Summary

We are generating a pipeline dynamically in our GitLab pipeline and include it. After upgrade to 17.3.1 this fails with the following error message in the Web UI:

Unable to create pipeline

Undefined error (01J6H6MCAB0NGMYEF2KCMVJSTJ)

It also states, the YAML is invalid.

see also: https://forum.gitlab.com/t/dynamic-job-failure-following-upgrade-of-self-hosted-gitlab-to-17-3-1/109891

Steps to reproduce

1. Create a project with a dynamic pipeline
2. Try to run the pipeline on 17.3.1

Example Project

What is the current bug behavior?

The pipeline executes the generator job and generates the pipeline, but the generated pipeline does not start, instead the error is shown.

What is the expected correct behavior?

The generated pipeline should start

Relevant logs and/or screenshots

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible workaround

Restarting your instance/pods should fix this issue.

You can check in two places via a database console if the conditions are right:

• Has the system recorded the corresponding migration as completed?
  • Use SELECT * FROM schema_migrations WHERE version = '20240708182825'; to verify
  • The expected output is one row with that version and a date.
• Does the max_artifacts_content_include_size field exist in the application_settings table?
  • Use SELECT max_artifacts_content_include_size FROM application_settings; to verify
  • The expected output is one row with just the 5242880 value.

If both these conditions are correct, please restart your instance. If you encounter unexpected conditions, or if restarting does not resolve the issue, let us know.