Stage dist-git clones fail as shown below:
[mprahl@mprahl-laptop tmp]$ git clone -q https://src.stg.fedoraproject.org/modules/testmodule.git error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500 Internal Server Error fatal: The remote end hung up unexpectedly
N/A
I cannot test MBS in stage, which keeps me from upgrading production.
This seems to be causing a pagure traceback, assigning to @pingou to look at (although it might also be repospanner / @puiterwijk )
Metadata Update from @kevin: - Issue assigned to pingou - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: src.fp.o
Looking at the traceback it seems to be an repospanner issue:
File "/usr/lib/python2.7/site-packages/pagure/ui/clone.py", line 232, in clone_proxy return proxy_repospanner(project, service) File "/usr/lib/python2.7/site-packages/pagure/ui/clone.py", line 176, in proxy_repospanner "X-Extra-project_namespace": project.namespace, File "/usr/lib/python2.7/site-packages/requests/api.py", line 50, in request response = session.request(method=method, url=url, **kwargs) File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 464, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 613, in send r.content File "/usr/lib/python2.7/site-packages/requests/models.py", line 733, in content self._content = bytes().join(self.iter_content(CONTENT_CHUNK_SIZE)) or bytes() File "/usr/lib/python2.7/site-packages/requests/models.py", line 659, in generate raise ChunkedEncodingError(e) ChunkedEncodingError: ('Connection broken: IncompleteRead(153 bytes read)', IncompleteRead(153 bytes read))
Metadata Update from @pingou: - Issue assigned to puiterwijk (was: pingou)
It seems repospanner has a permission issue:
panic serving 10.5.128.175:51478: open /var/lib/repospanner/gitstore/pagure/main/modules/testmodule/21/7e420f60b1204a2ea0ba7d7ad65a000afb0924: permission denied
I've just found out that this is currently blocking upgrade to new MBS version, because a) we are not able to test it on staging and b) we are not brave one to deploy it directly to prod. I find a) easier to fix :).
I've just found out that this is currently blocking upgrade to new MBS version
This issue should not block MBS upgrade - the problem described is specific to testmodule.git repository and a different repository, such as testmodule2.git, can be used for MBS testing purposes.
This was caused by a mis-start of repoSpanner at some point, causing this file to be root-owner... a chown should have fixed this.
Metadata Update from @puiterwijk: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
This problem was caused by me during December while trying to 'fix' another issue. Patrick is working on fixing my fixing.
Login to comment on this ticket.