new build host tcc-deb9build: failure to push manuals
For some reason, the new "tcc-deb9build" jenkins slave is unable to publish osmocom manuals, see https://jenkins.osmocom.org/jenkins/job/master-osmo-gsm-tester/a1=default,a2=default,a3=default,a4=default,label=osmocom-master-debian9/54/console
The ansible playbook has fully executed before, so either there's something incomplete in our playbook, or there's something wrong with connectivity between that build slave and the jenkins master.
#1 Updated by laforge over 1 year ago
- Status changed from New to In Progress
- Assignee changed from sysmocom to laforge
I manually logged onto the machine, and it is not a network problem. I can create a SSH connection to port 48 on rita.sysmocom.de:
ssh -p 48 email@example.com The authenticity of host '[rita.osmocom.org]:48 ([188.8.131.52]:48)' can't be established. ECDSA key fingerprint is SHA256:M/HqD/XAAhWv0wkGLaQTlYgSdowdDNtaA6+rsVmiw+I. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '[rita.osmocom.org]:48,[184.108.40.206]:48' (ECDSA) to the list of known hosts. Password for firstname.lastname@example.org:
The 'known hosts' issue is expected, but the jenkins job explicitly uses a separate known_hosts file:
osmocom-build@debian:~$ rsync -e "ssh -o 'UserKnownHostsFile=/home/osmocom-build/jenkins/workspace/master-osmo-gsm-tester/a1/default/a2/default/a3/default/a4/default/label/osmocom-master-debian9/osmo-gsm-manuals/build/known_hosts' -p 48" email@example.com:web-files/latest/ Password for firstname.lastname@example.org:
So it seems that somehow passing the credentials is not working as expected.