{"push_id":899881709,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"45ec263f3f0ea3e13d511c692dd3ff5114a5e6d9","before":"5fa258b7087e610625e0277efb197f87db08f1ea","commits":[{"sha":"b5b0b63e32800b3745a5d0e66ce434fed09ad6b7","author":{"email":"8bfd13cad0bc4b2ac41d9e235951e72c9b62c2aa@jvf.cc","name":"Jay Faulkner"},"message":"Run IPA in chroot instead of container in CoreOS\n\nsystemd-nspawn has been adding more and more security features, the\nlatest being /sys and /proc/sys being completely read only. This breaks\nseveral things IPA needs to do from the container, including the sysrq\ntriggers used for reboot.\n\nAdditionally, any downstream hardware manager that wants to implement\nsoftware RAID requires this fix, as mdadm needs to write to /sys to\nassemble arrays. Linux-IO has a similar issue with not operating in\na read only /sys environment.\n\nThis changes IPA to run in a chroot instead of a container. This should\nbe the same from the perspective of IPA, but have no security rules\nlimiting what we can do inside the ramdisk.\n\nCo-Authored-By: Alex Weeks <alex.weeks@gmail.com>\nChange-Id: I6a572bdd791841add913d33c5b79b59033c3f237\nCloses-bug: 1524033","distinct":true,"url":"https://api.github.com/repos/openstack/ironic-python-agent/commits/b5b0b63e32800b3745a5d0e66ce434fed09ad6b7"},{"sha":"45ec263f3f0ea3e13d511c692dd3ff5114a5e6d9","author":{"email":"d95b56ce41a2e1ac4cecdd398defd7414407cc08@review.openstack.org","name":"Jenkins"},"message":"Merge \"Run IPA in chroot instead of container in CoreOS\"","distinct":true,"url":"https://api.github.com/repos/openstack/ironic-python-agent/commits/45ec263f3f0ea3e13d511c692dd3ff5114a5e6d9"}]}