Jeremy Stanley email@example.com writes:
On 2017-09-25 10:51:42 -0400 (-0400), Doug Hellmann wrote:
I assume someone has already noticed that this release failed, but I'm
forwarding it to the dev list just in case.
Thanks for the heads up! And yes, it's currently under discussion in
openstack-infra but we're still trying to nail down the root cause.
We recently removed several Zuul mergers to reallocate them to Zuul v3
in preparation for the cutover. Unfortunately, the persistent
workspaces on the release worker have git repos which may have
originally been cloned from those mergers, and so when our release jobs
update those repos, they may consult those mergers as they are the
This is increasingly likely to affect projects created more recently, as
older projects would have been cloned when we had fewer mergers, and the
mergers we removed were the ones added last.
This is something that, ideally, we would have addressed either in
zuul-cloner or in the release jobs. However, we're about to replace
them all, so it's probably not worth worrying about.
In the mean time, I removed all of the workspaces on the release worker,
so all projects will clone anew from the existing set of mergers.