Bug 1639233 - Update nvdimm support with fixes from rhel
Summary: Update nvdimm support with fixes from rhel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F29FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2018-10-15 11:08 UTC by Radek Vykydal
Modified: 2018-10-22 16:13 UTC (History)
8 users (show)

Fixed In Version: anaconda-29.24.5-1 anaconda-29.24.7-1.fc29
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-22 16:13:43 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Radek Vykydal 2018-10-15 11:08:57 UTC 
Port of latest nvdimm support updates from rhel branch:

- allow bootloader on NVDIMM
- nvdimm commands for UI actions in generated kickstart
Comment 1 Radek Vykydal 2018-10-15 11:17:04 UTC 
https://github.com/rhinstaller/anaconda/pull/1658
Comment 2 Fedora Blocker Bugs Application 2018-10-15 12:34:02 UTC 
Proposed as a Freeze Exception for 29-final by Fedora user m4rtink using the blocker tracking app because:

 Anaconda recently gained support for using the new cutting edge NVDIMM storage technology and this is a batch of fixes related to it:

- allow bootloader on NVDIMM
- nvdimm commands for UI actions in generated kickstart

The NVDIMM support is fairly separate and isolated, so changes should not influence other storage/bootloader related code. Then fixes have also already been in use on one of the RHEL branches without any known issues.
Comment 3 Geoffrey Marr 2018-10-15 19:20:35 UTC 
Discussed during the 2018-10-15 blocker review meeting: [1]

The decision to classify this bug as an "AcceptedFreezeException" was made as hardware enablement in the installer is always desirable, and cannot be fixed with an update. As this is said to be fairly isolated from other storage code, the risk should be low.

[1] https://meetbot.fedoraproject.org/fedora-blocker-review/2018-10-15/f29-blocker-review.2018-10-15-16.00.txt
Comment 4 Fedora Update System 2018-10-18 14:05:07 UTC 
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
Comment 5 Fedora Update System 2018-10-18 14:07:13 UTC 
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
Comment 6 Fedora Update System 2018-10-20 19:22:44 UTC 
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
Comment 7 Fedora Update System 2018-10-22 16:13:43 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.