Bug 1953828

Summary: The param /boot/vmlinuz-5.11.14-300.fc34.x86_64 is incorrect
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: grubbyAssignee: Peter Jones <pjones>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: fmartine, pjones, rharwood
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-27 17:27:07 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 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 ***