When starting a new workspace from the Project Configurator, sometimes the config file is not present in the workspace

[jankeromnes]

Bug description

When a Project has a configuration saved in the Project DB, and there is no .gitpod.yml in the repository, the Project DB configuration should always be added into workspaces for that repository (as an untracked .gitpod.yml file).

However, in some cases, it seems that the Project DB config is not added to the workspaces.

Steps to reproduce

The expected flow is:

1. Add a Project, and get to the Configuration step
2. Edit the config, and click on Run Prebuild
3. Once the Prebuild is complete, click on New Workspace

Expected behavior

If the repository does not have a committed .gitpod.yml, the new workspace should have an untracked .gitpod.yml containing the config from the Project DB.

Additionally, all new workspaces for that repository should also have this untracked .gitpod.yml (until someone adds it to Git and starts versioning it).

However, sometimes the config is not present at all in the workspace.

Example repository

No response

Anything else?

Theory: Maybe it's added in the Prebuild (from the Project Configurator), but not in un-prebuilt workspaces? That would explain why, if the Prebuild fails, there is no config in the workspace.

[mikenikles]

I have received feedback from one of our community members who encounters that too.

[jldec]

/schedule

[roboquat]

@jldec: Issue scheduled in the meta team (WIP: 0)

In response to this:

/schedule

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[AlexTugarev]

We couldn't reproduce this issue. I also assume, some of this cases are linked to failed prebuilds, or to existing ones, so that it's not clear when to expect a dirty .gitpod.yml file to be contributed.

Let's reopen when we can actually reproduce this issue.