Since DNF 3.6 DNF reports module dependency issues and Anaconda should abort the installation if such issues are detected, like it already does with broken packages and groups. Otherwise there is the risk of silently installing a broken system. NOTE: As this change requires DNF >=3.6, it needs to be coordinated with a DNF update.
PR: https://github.com/rhinstaller/anaconda/pull/1642
Proposed as a Freeze Exception for 29-final by Fedora user m4rtink using the blocker tracking app because: Anaconda should make use of the new DNF 3.6 functionality to detect module dependency issues and abort the installation in such a case (as Anaconda already does for broken packages and groups). Otherwise there is a risk we will silently install a broken system.
3.6 already got pushed stable, so that's not a problem any more.
Discussed during the 2018-10-08 blocker review meeting: [1] The decision to classify this bug as an AcceptedFreezeException was made: "This is clearly a useful and sensible protection and cannot be added post-release" [1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2018-10-08/f29-blocker-review.2018-10-08-16.00.log.txt
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.