~otto-copilot/ols-jenkaas/jenkaas-recovery-20170914

« back to all changes in this revision

Viewing changes to setup/seeded-slave

  • Committer: Daniel Manrique
  • Date: 2017-09-11 18:54:33 UTC
  • mfrom: (506.1.1 seeded-failsafe)
  • Revision ID: roadmr@ubuntu.com-20170911185433-67vq945tyan5mldu
MergedĀ lp:~roadmr/ols-jenkaas/seeded-failsafe

Show diffs side-by-side

added added

removed removed

Lines of Context:
8
8
 
9
9
RELEASE=$(lsb_release -cs)
10
10
 
 
11
# Check the bot user has the required ssh public key.
 
12
HOST=${NODE_NAME}
 
13
KEY_NAME=jenkins@${HOST}
 
14
KEY_PATH=~/.ssh/${KEY_NAME}
 
15
 
 
16
if ! curl https://launchpad.net/~${JENKAAS_LANDING_USER}/+sshkeys | grep -q "$(cat ${KEY_PATH}.pub)"
 
17
then
 
18
    echo "[WARNING] ssh key not set up properly."
 
19
    echo "The public key generated with the seed-slave job must be added to ${JENKAAS_LANDING_USER}'s"
 
20
    echo "allowed SSH keys on Launchpad."
 
21
else
 
22
    echo "All good, ${JENKAAS_LANDING_USER} has this slave's SSH key set up properly."
 
23
fi
 
24
 
11
25
# FIXME: The missed packages (they should be installed in seed-slave), this
12
26
# is catching up and needs a better solution -- vila 2016-09-12
13
27
APT_OPTS="--option=Dpkg::Options::=--force-confold --option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet --no-install-recommends"