#1529 [Cloud SIG] Issue with lookaside cache
Closed: Fixed with Explanation by arrfab. Opened by jcapitao.

Hello,

I'm hitting issue when uploading sources to lookaside cache

$ /tmp/centos-git-common/lookaside_upload -f SOURCES/2.0.27.tar.gz -n uwsgi -b c10s-sig-cloud-openstack-epoxy
[+] CentOS Lookaside upload tool -> Checking if file already uploaded
[+] CentOS Lookaside upload tool -> Initialing new upload to lookaside
[+] CentOS Lookaside upload tool -> URL : https://git.centos.org
[+] CentOS Lookaside upload tool -> Source to upload : SOURCES/2.0.27.tar.gz
[+] CentOS Lookaside upload tool -> Package name: uwsgi
[+] CentOS Lookaside upload tool -> sha1sum: 63bee8ae6afbda2768a35f52f4cfd2174a68d29d
[+] CentOS Lookaside upload tool -> Remote branch: c10s-sig-cloud-openstack-epoxy
[+] CentOS Lookaside upload tool ->  ====== Trying to upload =======

######################################################################################################################################################################################################################################################### 100.0%curl: (22) The requested URL returned error: 403

[+] CentOS Lookaside upload tool -> [ERROR] Something didn't work to push to https://git.centos.org/sources/uwsgi/c10s-sig-cloud-openstack-epoxy/63bee8ae6afbda2768a35f52f4cfd2174a68d29d
[+] CentOS Lookaside upload tool -> [ERROR] Verify at the server side

I tried with another project, and the result is the same

[+] CentOS Lookaside upload tool -> Checking if file already uploaded
[+] CentOS Lookaside upload tool -> Initialing new upload to lookaside
[+] CentOS Lookaside upload tool -> URL : https://git.centos.org
[+] CentOS Lookaside upload tool -> Source to upload : SOURCES/websockify-0.12.0.tar.gz
[+] CentOS Lookaside upload tool -> Package name: python-websockify
[+] CentOS Lookaside upload tool -> sha1sum: ccd1783038ea2a94e604518535f812e8af670868
[+] CentOS Lookaside upload tool -> Remote branch: c10s-sig-cloud-openstack-epoxy
[+] CentOS Lookaside upload tool ->  ====== Trying to upload =======

######################################################################## 100.0%curl: (22) The requested URL returned error: 403

[+] CentOS Lookaside upload tool -> [ERROR] Something didn't work to push to https://git.centos.org/sources/python-websockify/c10s-sig-cloud-openstack-epoxy/ccd1783038ea2a94e604518535f812e8af670868
[+] CentOS Lookaside upload tool -> [ERROR] Verify at the server side

My TLS cert is valid, but maybe I don't have enough authorization. Though I don't know whether there is some ACL or not for such request.


Metadata Update from @arrfab:
- Issue assigned to arrfab

Metadata Update from @arrfab:
- Issue tagged with: authentication, cbs, medium-gain, medium-trouble

I had a quick look and it seems that https://fasjson.fedoraproject.org wasn't returning a matching group :

[Wed Oct 30 09:26:50.268244 2024] [cgid:error] [pid 3585431:tid 140390283843328] [client ip.add.ress:35051] [userna
me=jcapitao] Processing upload request: NAME=python-websockify BRANCH=c10s-sig-cloud-openstack-epoxy CHECKSUM=ccd17830
38ea2a94e604518535f812e8af670868/srv/cache/lookaside/python-websockify/c10s-sig-cloud-openstack-epoxy/srv/cache/lookas
ide/python-websockify/c10s-sig-cloud-openstack-epoxy/ccd1783038ea2a94e604518535f812e8af670868No matching group returne
dNo matching group returnedIssue verifying acl : /var/www/cgi-bin/upload.cgi

But I just queried myself fasjson and it's now returning correct group membership for you (including sig-cloud) ...
Worth retrying (in case it was a transient error to reach fasjson api endpoint) ?

For easier/faster debug, you know where to find me on irc too ;-)

also thinking about another potential candidate : the python re.match to detect branch/group :
https://github.com/CentOS/ansible-role-pagure/blob/master/files/8/upload.cgi.fasjson#L80

role modified and applied.
Thanks @zlopez for the regex tip !

@jcapitao already confirmed it's working so closing

Metadata Update from @arrfab:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

Log in to comment on this ticket.

Metadata