+++ This bug was initially created as a clone of Bug #1217578 +++ Working: http://koji.fedoraproject.org/koji/taskinfo?taskID=9518375 First failing: http://koji.fedoraproject.org/koji/taskinfo?taskID=9528133 This one looks like it was firewalling. I think the way to debug this is to look at the package diff between the installer ISOs. --- Additional comment from Colin Walters on 2015-04-30 13:30:04 EDT --- First failing with "umount failed" symptom: http://koji.fedoraproject.org/koji/taskinfo?taskID=9571961 --- Additional comment from Colin Walters on 2015-04-30 14:04:11 EDT --- http://pkgs.fedoraproject.org/cgit/ostree.git/commit/?id=b482182fce0dd99df1e65691ee9ea39d7a80358f --- Additional comment from Fedora Update System on 2015-04-30 14:57:01 EDT --- ostree-2015.5-5.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/FEDORA-2015-6034/ostree-2015.5-5.fc22 --- Additional comment from Fedora Blocker Bugs Application on 2015-05-01 10:24:06 EDT --- Proposed as a Freeze Exception for 22-final by Fedora user walters using the blocker tracking app because: Should fix the Atomic composes. --- Additional comment from Fedora Update System on 2015-05-01 12:37:33 EDT --- ostree-2015.5-5.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. This latest installer image does not have the above ostree fix: https://kojipkgs.fedoraproject.org/mash/branched-20150505/22/x86_64/os/images/
According to dgilmore, this was a releng issue - the update had not actually been properly pushed stable - and he's now fixed it. So, closing.