Some integration-slave-docker instances have been provisioned with a /var/lib/docker partition but others do not. It is a bit confusing.
$ sudo cumin --trace --force 'name:docker' 'mount -t ext4|sort' 13 hosts will be targeted: integration-slave-docker-[1021,1034,1037,1040-1041,1043,1048-1054].integration.eqiad.wmflabs
===== NODE GROUP ===== (3) integration-slave-docker-[1021,1049,1053].integration.eqiad.wmflabs ----- OUTPUT of 'mount -t ext4|sort' ----- /dev/mapper/vd-second--local--disk on /srv type ext4 (rw,relatime,data=ordered) /dev/vda3 on / type ext4 (rw,relatime,data=ordered)
===== NODE GROUP ===== (10) integration-slave-docker-[1034,1037,1040-1041,1043,1048,1050-1052,1054].integration.eqiad.wmflabs ----- OUTPUT of 'mount -t ext4|sort' ----- /dev/mapper/vd-docker on /var/lib/docker type ext4 (rw,relatime,data=ordered) /dev/mapper/vd-second--local--disk on /srv type ext4 (rw,relatime,data=ordered) /dev/vda3 on / type ext4 (rw,relatime,data=ordered) ================
Or in short, the following instances lack a /var/lib/docker dedicated partition:
integration-slave-docker-1021.integration.eqiad.wmflabs |
integration-slave-docker-1049.integration.eqiad.wmflabs |
integration-slave-docker-1053.integration.eqiad.wmflabs |
Maybe because they predate the introduction of /var/lib/docker and puppet is unable to magically shuffle the partitions for us. In which case we would have to provision new instances and delete those.