Forum archive
apt-get dist-upgrade uninstalled jenkins in turnkeylinux-jenkins VM?
Hi Guys,
I noticed today that my continuous integration server was down and upon investigation why, it turned out that jenkins was not even installed anymore!
In the apt log, I found this:
Start-Date: 2014-04-25 05:59:47
Commandline: /usr/bin/apt-get -o quiet=1 dist-upgrade -q -y -o APT::Get::Show-Up graded=true -o Dir::Etc::sourcelist=/etc/apt/sources.list.d/security.sources.lis t -o Dir::Etc::sourceparts=nonexistent -o DPkg::Options::=--force-confdef -o DPk g::Options::=--force-confold
Remove: openjdk-6-jre-lib:amd64 (6b27-1.12.6-1~deb7u1), openjdk-6-jre-headless:a md64 (6b27-1.12.6-1~deb7u1), ant:amd64 (1.8.2-4), jenkins:amd64 (1.560), ca-cert ificates-java:amd64 (20121112+nmu2), openjdk-6-jdk:amd64 (6b27-1.12.6-1~deb7u1), openjdk-6-jre:amd64 (6b27-1.12.6-1~deb7u1)
End-Date: 2014-04-25 05:59:50
So it seems that apt-get dist-upgrade ran silently last night and removed jenkins and related packages. This is on a turnkey debian 7 jenkins VM, installed through proxmox.
I have reinstalled jenkins with apt-get and everything is back up, but if someone can help me understand why this happend I would appreciate it. Seems strange that dist-upgrade uninstalls jenkins on a VM specifically configured to run jenkins.
If I need to investigate further or share more log files, let me know.
I just did a quick test install and when applying the security updates, you are right... It uninstalls Jenkins! I'm not sure what is going on but I will get Alon and/or Liraz on the job ASAP... Thanks for posting.
FWIW I have also lodged a bug on the TKL Issue Tracker.
It looks to me like the auto security updates are the culprit although I'm not sure why. My assumption is that there is something that is being upgraded that conflicts with Jenkins (or probably more likely one of it's dependencies) which is causing the uninstall. TBH I anticipate that it will uninstall Jenkins again tonight (when the security updates install again). I suspect that you may need to disable the auto security updates as a temporary workaround while we sort this out...