Git replication failing for new projects

Bug #1229151 reported by Julia Portnova
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
OpenStack Core Infrastructure
Fix Released
Medium
Unassigned

Bug Description

All Manila jobs failed

2013-09-23 11:22:25.634 | + git clone git://git.openstack.org/stackforge/manila .
2013-09-23 11:22:25.728 | warning: remote HEAD refers to nonexistent ref, unable to checkout.

https://review.openstack.org/#/c/47814/
http://logs.openstack.org/14/47814/1/check/gate-manila-pep8/4d774c7/console.html

description: updated
Revision history for this message
Jeremy Stanley (fungi) wrote :

It looks like the replication from review.openstack.org to the gitXX.openstack.org server farm may be failing, at least for newly-added projects. Looking into the cause now.

summary: - Manila jobs fail
+ Git replication failing for new projects
Changed in openstack-ci:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Jeremy Stanley (fungi)
Revision history for this message
Jeremy Stanley (fungi) wrote :

After forcing replication for the specific new projects affected through gerrit's SSH API and waiting a minute, the HEADs for the corresponding bare repos on each server in the git farm contained a reference to a viable (master) branch and could be cloned from successfully. This is most likely a race condition in manage-projects not waiting long enough to trigger replication from Gerrit.

tags: added: jeepyb low-hanging-fruit
Changed in openstack-ci:
status: In Progress → Triaged
status: Triaged → Confirmed
assignee: Jeremy Stanley (fungi) → nobody
Jeremy Stanley (fungi)
Changed in openstack-ci:
importance: High → Medium
Jeremy Stanley (fungi)
Changed in openstack-ci:
milestone: none → icehouse
Revision history for this message
Noorul Islam K M (noorul) wrote :

https://review.openstack.org/#/c/54877/

Is this also the reason for above review to to fail?

Revision history for this message
James E. Blair (corvus) wrote :

We believe the race conditions in new project creation that caused this have been addressed.

Changed in openstack-ci:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.