Description of problem: By default the Atomic Host install class doesn't get chosen, which means things like having an XFS filesystem on root by default doesn't happen. We can further see this by looking at OpenQA where we should see a fedora atomic image rather than a blank image on this screen: https://openqa.fedoraproject.org/tests/296798#step/_boot_to_anaconda/3 Version-Release number of selected component (if applicable): anaconda 29.24.3-2.fc29 How reproducible: Always
proposed fix: https://github.com/rhinstaller/anaconda/pull/1661
Proposed as a Freeze Exception for 29-final by Fedora user dustymabe using the blocker tracking app because: Would be nice for the proper installclass to be used on Atomic Host ISO media. The upstream patch to anaconda is trivial so hopefully low risk especially for any non Atomic* artifacts.
+1 FE
anaconda-29.24.6-1.fc29 dnf-4.0.4-1.fc29 dnf-plugins-core-4.0.0-2.fc29 libblockdev-2.20-2.fc29 libdnf-0.22.0-2.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-2789f6b6e7
anaconda-29.24.7-1.fc29, dnf-4.0.4-1.fc29, dnf-plugins-core-4.0.0-2.fc29, libblockdev-2.20-2.fc29, libdnf-0.22.0-5.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-2789f6b6e7
anaconda-29.24.7-1.fc29, dnf-4.0.4-1.fc29, dnf-plugins-core-4.0.0-2.fc29, libblockdev-2.20-2.fc29, libdnf-0.22.0-5.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.