Bug 1713441
| Summary: | Post upgrade from F29 to F30 mdadm.conf references wrong device | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ivor Durham <ivor.durham> |
| Component: | mdadm | Assignee: | Jes Sorensen <jes.sorensen> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 31 | CC: | agk, dledford, jes.sorensen, xni |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-24 16:47:33 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Ivor Durham
2019-05-23 16:44:55 UTC
I've discovered that this problem depends on which kernel is booted. I use the system in question as a server and usually access it over the network. So after the F29->F30 upgrade I hadn't noticed that instead of booting the default kernel, the system was booting the rescue kernel (see Bug #1707621 which is resolved by re-installing grub2 on /dev/sda). If I manually selected the most recent F30 kernel, the RAID device was /dev/md/pv00 as expected and consistent with /etc/mdadm.conf. However, when the rescue kernel was booted automatically, the RAID device becomes /dev/md/clowder:pv00: Booting vmlinuz-5.0.16-300.fc30.x86_64 establishes /dev/md/pv00 Booting vmlinuz-0-rescue-3b4d4e3f6de743b2a10dd1bf715f70c4 establishes /dev/md/clowder:pv00 This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31. This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |