Bug #4276


update-osmo-ci-on-slaves fails on build2-deb8build-ansible

Added by osmith about 4 years ago. Updated about 4 years ago.

Target version:
Start date:
Due date:
% Done:


Spec Reference:


The job runs fine on all other hosts, but on build2-deb8build-ansible it fails to rebuild the docker image:

cgroups: cannot find cgroup mount destination: unknown

I found this thread, with a proposed workaround:

Temp fix:
sudo mkdir /sys/fs/cgroup/systemd
sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd

So my guess is, that /sys/fs/cgroup/systemd is not mounted properly on the system?

FWIW, on my debian 9 installation, building the image works and /sys/fs/cgroup/systemd seems to get mounted automatically by systemd at boot. It is not in /etc/fstab.

Maybe a simple reboot fixes this. Can somebody with access to the server have a look at it?

Actions #1

Updated by laforge about 4 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 40

I just created that directory and mounted cgroupfs. I also added it to /etc/fstab, unmounted the manual mount and re-mounted it with 'mount -a', which worked. So I think even after reboot the directory/mount should now exist.

Actions #2

Updated by laforge about 4 years ago

  • Status changed from In Progress to Resolved
  • Assignee changed from 4368 to laforge
  • % Done changed from 40 to 100

the problem was more complex. There was some feed installed, and parts of the system were using that (particularly for systemd). Due to some dependency nightmare, only libsystemd but no systemd package was installed anymore, and systemd was uninstallable. Manual deinstallation of the bpo packages and reinstallation from the normal jessie feeed helped. Once systemd was present agian, the cgroup mounting problem was gone.


Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)