I just noticed this in the gate.
2018-11-19 05:48:00.238 14608 WARNING tripleoclient.v1.tripleo_deploy.Deploy [ ] "2018-11-19 05:45:06,816 ERROR: 8688 -- Failed running docker-puppet.py for ironic",
2018-11-19 05:48:00.239 14608 WARNING tripleoclient.v1.tripleo_deploy.Deploy [ ] "2018-11-19 05:45:06,816 ERROR: 8688 -- container create failed: container_linux.go:336: starting container process caused \"process_linux.go:293: applying cgroup configuration for process caused \\\"open /sys/fs/cgroup/cpuset/machine.slice/cpuset.cpus: no such file or directory\\\"\"",
2018-11-19 05:48:00.239 14608 WARNING tripleoclient.v1.tripleo_deploy.Deploy [ ] ": internal libpod error",
2018-11-19 05:48:00.239 14608 WARNING tripleoclient.v1.tripleo_deploy.Deploy [ ] "",
http://logs.openstack.org/57/614457/10/check/tripleo-ci-centos-7-containers-multinode/19ea5bb/logs/undercloud/home/zuul/install-undercloud.log.txt.gz#_2018-11-19_05_48_00_238
logstash query shows this failure happens from time to time.
Looks like some kind of race, but digging a little it seems there are some races in runc[1], which seems fixed sometime back. May be we're using an older runc?
[1] https://github.com/opencontainers/runc/pull/1683
It does not look like related to the runc pull request mentioned above. The fix seems to be there in libpod[1]. I guess this needs further investigation.
[1] https:/