#860 New branches are created with wrong permissions in https://git.centos.org/sources
Closed: Fixed 2 years ago by arrfab. Opened 2 years ago by amoralej.

In the last days we've found twice that, when uploading tarballs with lookaside_upload to new branches, the permissions are incorrectly set and the script fails with:

/tmp/scratch_dir/centos-git-common/lookaside_upload -f SOURCES/msgpack-1.0.4.tar.gz -n python-msgpack -b c9s-sig-cloud-openstack-zed
[+] 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/msgpack-1.0.4.tar.gz
[+] CentOS Lookaside upload tool -> Package name: python-msgpack
[+] CentOS Lookaside upload tool -> sha1sum: 422a0982aba597ad193732965db933dda52255a3
[+] CentOS Lookaside upload tool -> Remote branch: c9s-sig-cloud-openstack-zed
[+] CentOS Lookaside upload tool -> ====== Trying to upload =======

################################################################## 100.0%
################################################################## 100.0%

File msgpack-1.0.4.tar.gz stored OK (checksum 422a0982aba597ad193732965db933dda52255a3 , size 52904)
[+] CentOS Lookaside upload tool -> Validating that source was correctly uploaded ....
/tmp/scratch_dir/centos-git-common/lookaside_upload: line 117: [: : integer expression expected
[+] CentOS Lookaside upload tool -> [ERROR] it seems there is a mismatch with source size and remote file size

Debugging it, we found it that we get 403 error from https://git.centos.org/sources/python-msgpack/c9s-sig-cloud-openstack-zed/

Fabian checked that the permissions are wrong and set them properly manually.

We've hit this with both python-msgpack and python-textfsm but not for other packages where we've also created new branches so it seems there is some randomness.


Metadata Update from @arrfab:
- Issue assigned to arrfab
- Issue tagged with: cbs, high-gain, medium-trouble

2 years ago

"Amusingly" I wasn't able to reproduce that issue, but still sligthly changed in the .cgi script the way perms on newly created directories are set.

Closing for now but feel free to reopen if it happens again for new directories/branches

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

2 years ago

Login to comment on this ticket.

Metadata
Boards 1
CBS Status: Backlog