Right, if memory serves, you observed that trying to cache git repositories as a part of building nodepool images while we were creating a new project in Gerrit, so nodepool scripts tried to clone a new project listed in the projects.yaml while it was still in the process of being added to the git server farm. That shouldn't happen in devstack-gate jobs themselves because they only update repositories which have already been pre-cached on their images, at which point the repositories will already be on the git server farm.
Right, if memory serves, you observed that trying to cache git repositories as a part of building nodepool images while we were creating a new project in Gerrit, so nodepool scripts tried to clone a new project listed in the projects.yaml while it was still in the process of being added to the git server farm. That shouldn't happen in devstack-gate jobs themselves because they only update repositories which have already been pre-cached on their images, at which point the repositories will already be on the git server farm.