Bug 1953828 - The param /boot/vmlinuz-5.11.14-300.fc34.x86_64 is incorrect
Summary: The param /boot/vmlinuz-5.11.14-300.fc34.x86_64 is incorrect
Keywords:
Status: CLOSED DUPLICATE of bug 1940298
Alias: None
Product: Fedora
Classification: Fedora
Component: grubby
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-27 04:05 UTC by Chris Murphy
Modified: 2022-04-27 17:27 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-04-27 17:27:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Chris Murphy 2021-04-27 04:05:01 UTC
Description of problem:

--update-kernel=/path/to/vmlinuz returns an error

--set-default=/path/to/vmlinuz works fine. Same path.




Version-Release number of selected component (if applicable):
grubby-8.40-51.fc34.x86_64

How reproducible:
Always

Steps to Reproduce:
1. grubby --args=tonk --update-kernel=/boot/vmlinuz-5.11.14-300.fc34.x86_64
2.
3.

Actual results:

The param /boot/vmlinuz-5.11.14-300.fc34.x86_64 is incorrect


Expected results:

Should work.


Additional info:

--update-kernel=ALL succeeds and does the right thing as well.

Same problem happens with --remove-args=


grubby --remove-args=tonk --update-kernel=/boot/boot/vmlinuz-5.11.16-300.fc34.x86_64

That works. Hmm. Which means this is a variant and duplicate of bug 1940298.

Comment 1 Robbie Harwood 2022-04-27 17:27:07 UTC

*** This bug has been marked as a duplicate of bug 1940298 ***


Note You need to log in before you can comment on or make changes to this bug.