poor interaction with thin clones

Bug #1195666 reported by Robert Collins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Core Infrastructure
Expired
Medium
Unassigned

Bug Description

Updating a thin clone of e.g. nova from review.openstack.org fails, but updating it from the github copy works.

To reproduce, make a thin clone from r.o.o, then let something get committed, then git pull and watch it fail.

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

When you say "from review.openstack.org" what protocol do you mean? If this is HTTPS it's hitting an overlaid local replica served via Apache. If this is SSH it's hitting a jgit service embedded within the Gerrit JVM. Knowing whether it's one or both exhibiting this issue might help narrow down the cause.

Revision history for this message
Robert Collins (lifeless) wrote :
Revision history for this message
Jeremy Stanley (fungi) wrote :

Interesting... that's definitely being proxied through to the Jetty Web server inside Gerrit's JVM, as opposed to https://review.openstack.org/p/openstack/quantum.git which would have hit the local /var/lib/git clone being served from the filesystem by Apache on the same server. It sounds like either there's something not quite right about the copy in the gerrit account's homedir (which is what Jetty serves up), or possibly it's a bug in Gerrit or Jetty.

Changed in openstack-ci:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Jeremy Stanley (fungi) wrote :

Perhaps we should also consider adding smarter Apache rewrite filters to redirect the above URL format (the one without /p) to also hit the local repository clones instead of Jetty.

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

We should see if this is still an issue with gerrit 2.8

James E. Blair (corvus)
Changed in openstack-ci:
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Core Infrastructure because there has been no activity for 60 days.]

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

Other bug subscribers

Remote bug watches

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