Why are you pushing 1.9 when 1.10.x has been in updates-testing for ages? E.g. FEDORA-2016-41a553b86c

The update does not work correctly when using nested slices.

For example,

sudo docker run -c=100 --cgroup-parent=machine-test.slice -it --rm busybox
Warning: '-c' is deprecated, it will be replaced by '--cpu-shares' soon. See usage.
/ # Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning.
/ # cat /proc/self/cgroup
10:freezer:/machine-test.slice/docker-30e173ed4a7bdb7ad943fc765010b7415f9b41d9d3ffd85f706da0b5db36494b.scope
9:devices:/machine-test.slice/docker-30e173ed4a7bdb7ad943fc765010b7415f9b41d9d3ffd85f706da0b5db36494b.scope
8:cpuset:/machine-test.slice/docker-30e173ed4a7bdb7ad943fc765010b7415f9b41d9d3ffd85f706da0b5db36494b.scope
7:blkio:/machine-test.slice/docker-30e173ed4a7bdb7ad943fc765010b7415f9b41d9d3ffd85f706da0b5db36494b.scope
6:perf_event:/machine-test.slice/docker-30e173ed4a7bdb7ad943fc765010b7415f9b41d9d3ffd85f706da0b5db36494b.scope
5:hugetlb:/machine-test.slice/docker-30e173ed4a7bdb7ad943fc765010b7415f9b41d9d3ffd85f706da0b5db36494b.scope
4:net_cls,net_prio:/machine-test.slice/docker-30e173ed4a7bdb7ad943fc765010b7415f9b41d9d3ffd85f706da0b5db36494b.scope
3:memory:/machine-test.slice/docker-30e173ed4a7bdb7ad943fc765010b7415f9b41d9d3ffd85f706da0b5db36494b.scope
2:cpu,cpuacct:/machine-test.slice/docker-30e173ed4a7bdb7ad943fc765010b7415f9b41d9d3ffd85f706da0b5db36494b.scope
1:name=systemd:/machine.slice/machine-test.slice/docker-30e173ed4a7bdb7ad943fc765010b7415f9b41d9d3ffd85f706da0b5db36494b.scope

The cgroup path is only correct for name=systemd, but is wrong for rest.