On 24/08/18 02:13, Colin Walters wrote: > See: > https://pagure.io/fedora-atomic-host-continuous/issue/24 > > https://ci.centos.org/artifacts/sig-atomic/fahc/rdgo/build > should be a symlink, but is rendering as a regular file. > Some sort of nginx frontend config change? > > Is the source code to the config management/kube objects/whatever > for stuff like the artifacts nginx public somewhere so I could look at `git log`? > > I wouldn't say we're blocked, I can figure out some other > place to sync our content and point other things at it, but > hopefully it's an easy fix and I won't have to. > I confirm that there was no config change at the nginx level, but that there was an issue wrt rsync to the artifacts storage node. I just had a quick look and it's *not* a symlink on that box either, so was wondering if it's a symlink at the src side. Due to the fact that the storage box was itself updated/restarted during the maintenance window, we suffered from a rsync 3.0 => 3.1 (landed in 7.5) issue, that was fixed by this commit : commit 26b49f2cf0e6bf401b9248f6fa2b76dcd2020036 Author: Fabian Arrotin <arrfab at centos.org> Date: Thu Aug 23 13:51:05 2018 +0200 added "fake super" option for rsyncd.conf, as update to rsync 3.1.2 blocked CI projects from uploading to artifacts (see https://bugzilla.redhat.com/show_bug.cgi?id=1506234) That solved the "operation not permitted" issue that some projects had when pushing to artifacts (discussed in #centos-devel) Can you verify that if src is a symlink on your side and that you rsync to artifacts, that issue is still there ? (aka consider a file and not a symlink at all) -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/ci-users/attachments/20180824/af483aef/attachment-0005.sig>