Miscellaneous Projects » Core testing infrastructure

already 28GB recovered by 'docker system prune' by now, and still runnning.

Total reclaimed space: 38.19GB

There is an ansible rule that sets up a cron job to run docker-cleanup.sh: https://gerrit.osmocom.org/c/osmo-ci/+/7716/

This has been set up on the rpi nodes successfully:

# cat /var/spool/cron/crontabs/osmocom-build
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/crontabPVPUxS installed on Mon Mar  8 09:17:27 2021)
# (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
#Ansible: cleanup-docker-images
0 */3 * * * test -x /home/osmocom-build/osmo-ci/scripts/docker-cleanup.sh && /home/osmocom-build/osmo-ci/scripts/docker-cleanup.sh >/dev/null

However, the cron job did not get executed because the file was owned by the wrong uid 1001 instead of 1000:

# ls -l /var/spool/cron/crontabs/
total 4
-rw------- 1 1001 crontab 366 Mar  8 09:17 osmocom-build

• there was a "pi" user with uid=1000
• existing ansible rules created "osmocom-build" without specifying the uid, so it became uid=1001
• running the docker role created the crontab with uid=1001
• as docker-playground.git assumes that its containers run as uid=1000, I had modified the ansible rules to remove the "pi" user and set "osmocom-build"'s uid to 1000
  • https://gerrit.osmocom.org/c/osmo-ci/+/23275/1
  • https://gerrit.osmocom.org/c/osmo-ci/+/23274/1
• after running the updated rule, ansible changed the uid of the already created user to 1000 but did not change ownership of the crontab file

So it's a problem with these three provisioned nodes specifically and won't happen when we provision new nodes. I've changed ownership of the file manually on these three:

# chown osmocom-build /var/spool/cron/crontabs/osmocom-build
# systemctl restart cron

I'll check back later to verify that the cronjob actually ran and then I'll close this issue.

Working as expected.