clean up still interfering with builds about buildfarm_deployment HOT 6 CLOSED

It also looks like that the cleanup log file does not contain any output for the last 17h.

from buildfarm_deployment.

Trying to run the cleanup script manually on one of the slaves:

Traceback (most recent call last):
  File "/home/jenkins-slave/cleanup_docker_images.py", line 4, in <module>
    import dateutil.parser
ImportError: No module named 'dateutil'

from buildfarm_deployment.

Did you also resolve the duplicate cronjobs?

from buildfarm_deployment.

Yeah, in the 1st commit, 495d802. The ensure absent was there, but it didn't specify the user, and the default was 'root' not 'jenkins-slave' 495d802#diff-a2052a49729c2f5f50ebbc65e3d02352R163

I also added the cleanup rule for the repo. The job does not exist on the master so I didn't add a cleanup for it.

from buildfarm_deployment.

Also, since the last run, I verified the cronjob has gone away:

# HEADER: This file was autogenerated at 2015-02-16 23:30:11 +0000 by puppet.
# HEADER: While it can still be managed manually, it is definitely not recommended.
# HEADER: Note particularly that the comments starting with 'Puppet Name' should
# HEADER: not be deleted, as doing so could cause duplicate cron jobs.
# Puppet Name: docker_cleanup_images
15 */2 * * * bash -c "python3 -u /home/jenkins-slave/cleanup_docker_images.py"

from buildfarm_deployment.

This seems to happen again:

• http://54.183.26.131:8080/job/Ibin_uS32__controller_manager__ubuntu_saucy_i386__binary/2/
• http://54.183.26.131:8080/job/Ibin_uS32__forward_command_controller__ubuntu_saucy_i386__binary/2/
• http://54.183.26.131:8080/job/Ibin_uS32__cob_default_robot_config__ubuntu_saucy_i386__binary/2/

from buildfarm_deployment.