Project

General

Profile

Actions

Bug #3772

closed

new build host tcc-deb9build: failure to push manuals

Added by laforge about 5 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Target version:
-
Start date:
01/31/2019
Due date:
% Done:

80%

Spec Reference:

Description

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.


Related issues

Related to Cellular Network Infrastructure - Bug #3725: Jenkins isn't using the credentials store for uploading to rita.osmocom.orgResolvedosmith12/12/2018

Actions
Actions #1

Updated by laforge about 5 years ago

  • Status changed from New to In Progress
  • Assignee changed from 4368 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 docs@rita.osmocom.org
The authenticity of host '[rita.osmocom.org]:48 ([144.76.43.76]: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,[144.76.43.76]:48' (ECDSA) to the list of known hosts.
Password for docs@ftp.osmocom.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" docs@rita.osmocom.org:web-files/latest/
Password for docs@ftp.osmocom.org:

So it seems that somehow passing the credentials is not working as expected.

Actions #2

Updated by laforge about 5 years ago

It appears we're still not using the jenkins credential store/passing system for the keys to push api/docs/binaries. I've manually added the public key from the new buildhost to ftp.osmocom.org now.

Actions #3

Updated by laforge about 5 years ago

  • % Done changed from 0 to 80
Actions #4

Updated by osmith about 5 years ago

Yes, still need an answer for that in #3725.

Actions #5

Updated by osmith about 5 years ago

  • Related to Bug #3725: Jenkins isn't using the credentials store for uploading to rita.osmocom.org added
Actions #6

Updated by laforge over 4 years ago

  • Status changed from In Progress to Rejected

that build host is no longer available to us anyway :/

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)