setenforce 0 does not fully disable selinux
create an empty directory somewhere, say, /mumble
yum --installroot=/mumble groupinstall Base
watch all of the postinstall scripts fail
Which begs the question: why does selinux mishandle chroot environments this way
(subject of another bug report).
I have a better understanding of what was happening with this example, and I
think the bug should be closed. Certainly, it's not high priority. I'm closing