Project creation using instance template sometimes fails
Please note that this is an intermittent bug.
Project creation using instance template sometimes skips the import process and creates an empty project instead. This was discovered by the
qa/qa/specs/features/ee/browser_ui/1_manage/project/project_templates_spec.rb end to end test.
Steps to reproduce
- Create a project with some files
- Use the project as an instance template (Admin Area > Settings > Templates > Custom project templates)
- Go to create new project page > "Create from template" tab > "Instance" tab
- Click "Use Template"
- Create a project.
Ideally, you should see "Import in progress" with a spinner. But sometimes, you land directly on a new, empty project.
This can be reproduced by running the e2e test
project_templates_spec a few times with:
CHROME_HEADLESS=false bin/qa Test::Instance http://localhost:3001 qa/specs/features/ee/browser_ui/1_manage/project/project_templates_spec.rb --tag quarantine --seed 44521
(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)
(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)
What is the current bug behavior?
The process of project creation using an instance level template skips the Import process and creates an empty project.
What is the expected correct behavior?
The process of project creation using an instance level template should import the template and the created project should have the files from the template project.
Relevant logs and/or screenshots
This is a video of e2e test running:
The template that was set at instance level:
Contents of the template: