Bug 2271186
| Summary: | RFE: Update package Recommends to specify sdubby as alternative to grubby | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gary Buhrmaster <gary.buhrmaster> | ||||
| Component: | kdump-utils | Assignee: | Coiby <coxu> | ||||
| Status: | CLOSED EOL | QA Contact: | |||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 40 | CC: | bhe, coxu, jeremy.linton, lichliu, ruyang, ryncsn, yangrr.2009 | ||||
| Target Milestone: | --- | Keywords: | RFE | ||||
| Target Release: | --- | Flags: | fedora-admin-xmlrpc:
mirror+
|
||||
| Hardware: | Unspecified | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2025-05-16 08:00:29 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 2271533 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Gary Buhrmaster
2024-03-23 13:43:23 UTC
Created attachment 2023217 [details]
Proposed patch for kexec-tools.spec file
Note that until recently, sdubby had a "Provides: grubby" stanza, but that was removed recently. Adding in sdubby as meeting the recommends returns kexec-tools to approximate equivalency before that other fix in sdubby. Related (where sdubby no longer provides grubby): Bug 2269992 This should probably wait in Bug 2271533 being resolved. I note that some code paths depend on the --update-kernel=ALL parm to grubby. This is currently not supported by sdubby. I have added a dependency on Bug 2271533 which requests support for --update-kernel=ALL to sdubby. Did kdumpctl change, because kdump was one of the reasons I went for the "emulate grubby" path, and kdumpctl was working on systemd-boot for a while. (In reply to Jeremy Linton from comment #5) > Did kdumpctl change, because kdump was one of the reasons I went for the > "emulate grubby" path, and kdumpctl was working on systemd-boot for a while. I do not think kdumpctl itself changed. However, when sdubby no longer provided grubby, the Recommends: grubby could no longer be satisfied with sdubby (before it could), which was the reason for the suggested change in the Recommend. However, there are some code paths in kdumpctl which seem to use --update-kernel=ALL, but some do not. Those that do not *probably* work if sdubby is installed (I have not personally tested it, but a skim of the code suggests it should). This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. 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 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed. |