Looks like the artifact box doesn't allow rsync access from the EC2 nodes (at least not the metal ones), since all attempts end up with:
# rsync -vvv --password-file=.rsync-passwd.ybZ -av "vagrant_boxes" systemd@artifacts.ci.centos.org::systemd/ opening tcp connection to artifacts.ci.centos.org port 873 Connected to artifacts.ci.centos.org (172.19.0.7) msg checking charset: UTF-8 sending daemon args: --server -vvvvlogDtpre.iLsfxC . systemd/ (4 args) @ERROR: access denied to systemd from UNKNOWN (172.27.24.172) [sender] _exit_cleanup(code=5, file=main.c, line=1661): entered rsync error: error starting client-server protocol (code 5) at main.c(1661) [sender=3.1.3] [sender] _exit_cleanup(code=5, file=main.c, line=1661): about to call exit(5)
/cc @arrfab
Metadata Update from @arrfab: - Issue assigned to arrfab
Metadata Update from @arrfab: - Issue tagged with: centos-ci-infra, high-gain, low-trouble
It's true that actual artifacts box had a rule to only allow rsync (unencrypted) from internal CI network/vlan/subnet. It was modified to now also include the remote AWS VPC subnets, coming in through vpn. Can you confirm that it's working for you now ? We still have to announce the switch to new setup (hosted at AWS side) and so migration soon
It seems to be working:
# hostname n27-24-55.pool.ci.centos.org # echo "Hello from EC2" >hello_world.txt # rsync --password-file=rsync.key -av hello_world.txt systemd@artifacts.ci.centos.org::systemd/ sending incremental file list sent 54 bytes received 12 bytes 132.00 bytes/sec total size is 15 speedup is 0.23 # curl -s http://artifacts.ci.centos.org/systemd/hello_world.txt Hello from EC2
Thanks!
Metadata Update from @mrc0mmand: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.