Re: [Release-job-failures] Release of openstack/puppet-nova for ref refs/tags/15.6.0 failed
Interesting. The tag was pushed but upload-git-mirror role failed: https://22ce6cebe995c8915d66-868b7eb6ba44b32e3b412bc5acf60e73.ssl.cf5.rackcd... Is this a known issue? On Thu, Jun 18, 2020 at 2:23 PM <zuul@openstack.org> wrote:
Build failed.
- openstack-upload-github-mirror https://zuul.opendev.org/t/openstack/build/fd8c86f9b57947239bd0273424e1d4d5 : FAILURE in 2m 30s - release-openstack-puppet https://zuul.opendev.org/t/openstack/build/05dd9c7ffdc74af5ae4065eb16a522f9 : SUCCESS in 5m 40s - announce-release https://zuul.opendev.org/t/openstack/build/188851ebacf9455ab50edc2101ae02bc : SUCCESS in 5m 31s
_______________________________________________ Release-job-failures mailing list Release-job-failures@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures
-- Emilien Macchi
On Thu, Jun 18, 2020, at 11:49 AM, Emilien Macchi wrote:
Interesting. The tag was pushed but upload-git-mirror role failed: https://22ce6cebe995c8915d66-868b7eb6ba44b32e3b412bc5acf60e73.ssl.cf5.rackcd...
Is this a known issue?
Was this a re-enqueue? It failed because the tag already existed on the remote: 2020-06-18 18:07:39.509620 | localhost | ! [remote rejected] 15.6.0 -> 15.6.0 (cannot lock ref 'refs/tags/15.6.0': reference already exists) If the content on github looks up to date and correct then I don't think there is anything else to do here.
On Thu, Jun 18, 2020 at 2:23 PM <zuul@openstack.org> wrote:
Build failed.
- openstack-upload-github-mirror https://zuul.opendev.org/t/openstack/build/fd8c86f9b57947239bd0273424e1d4d5 : FAILURE in 2m 30s - release-openstack-puppet https://zuul.opendev.org/t/openstack/build/05dd9c7ffdc74af5ae4065eb16a522f9 : SUCCESS in 5m 40s - announce-release https://zuul.opendev.org/t/openstack/build/188851ebacf9455ab50edc2101ae02bc : SUCCESS in 5m 31s
_______________________________________________ Release-job-failures mailing list Release-job-failures@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures
-- Emilien Macchi
Interesting. The tag was pushed but upload-git-mirror role failed: https://22ce6cebe995c8915d66-868b7eb6ba44b32e3b412bc5acf60e73.ssl.cf5.rackcd...
Is this a known issue? Was this a re-enqueue? It failed because the tag already existed on the remote:
2020-06-18 18:07:39.509620 | localhost | ! [remote rejected] 15.6.0 -> 15.6.0 (cannot lock ref 'refs/tags/15.6.0': reference already exists)
If the content on github looks up to date and correct then I don't think there is anything else to do here.
I don't think this was a reenqueue. Do we have another process that syncs things to GitHub? Maybe a race between the release pushing the mirror update and something else sneaking in and syncing it first? Either way, looks like things are up to date on GitHub and nothing else to do here. Sean
On Thu, Jun 18, 2020, at 11:55 AM, Sean McGinnis wrote:
Interesting. The tag was pushed but upload-git-mirror role failed: https://22ce6cebe995c8915d66-868b7eb6ba44b32e3b412bc5acf60e73.ssl.cf5.rackcd...
Is this a known issue? Was this a re-enqueue? It failed because the tag already existed on the remote:
2020-06-18 18:07:39.509620 | localhost | ! [remote rejected] 15.6.0 -> 15.6.0 (cannot lock ref 'refs/tags/15.6.0': reference already exists)
If the content on github looks up to date and correct then I don't think there is anything else to do here.
I don't think this was a reenqueue. Do we have another process that syncs things to GitHub? Maybe a race between the release pushing the mirror update and something else sneaking in and syncing it first?
Either way, looks like things are up to date on GitHub and nothing else to do here.
Sean
There were two github mirror jobs for puppet-nova running at roughly the same time. One succeeded (and pushed the tag) and the other failed. SUCCESS: https://zuul.openstack.org/build/1f363ade2d8d4f418db86ae33d2c3363/log/job-ou... FAILURE: https://zuul.openstack.org/build/fd8c86f9b57947239bd0273424e1d4d5/log/job-ou... This looks like a race between the job for the 16.4.0 and 15.6.0 tags. We could update the job to check for this particular failure case and treat it as a success assuming something else has merged. We could serialize these jobs between different events on the same repo. We can also just ignore it for now since everything is happy :)
Was this a re-enqueue? It failed because the tag already existed on the remote:
2020-06-18 18:07:39.509620 | localhost | ! [remote rejected] 15.6.0 -> 15.6.0 (cannot lock ref 'refs/tags/15.6.0': reference already exists)
If the content on github looks up to date and correct then I don't think there is anything else to do here. I don't think this was a reenqueue. Do we have another process that syncs things to GitHub? Maybe a race between the release pushing the mirror update and something else sneaking in and syncing it first?
Either way, looks like things are up to date on GitHub and nothing else to do here.
Sean There were two github mirror jobs for puppet-nova running at roughly the same time. One succeeded (and pushed the tag) and the other failed.
SUCCESS: https://zuul.openstack.org/build/1f363ade2d8d4f418db86ae33d2c3363/log/job-ou... FAILURE: https://zuul.openstack.org/build/fd8c86f9b57947239bd0273424e1d4d5/log/job-ou...
This looks like a race between the job for the 16.4.0 and 15.6.0 tags.
We could update the job to check for this particular failure case and treat it as a success assuming something else has merged. We could serialize these jobs between different events on the same repo. We can also just ignore it for now since everything is happy :) That would make sense I think. We were trying to update GitHub, but it responds telling us it already has the update. So if we can detect that is the error and just move along, all's good in the end.
participants (3)
-
Clark Boylan
-
Emilien Macchi
-
Sean McGinnis