Bug 1725720

Summary:	"man grubby" tells you not to run it. But grubby is the new official way to change boot options
Product:	[Fedora] Fedora	Reporter:	Alan Jenkins <alan.christopher.jenkins>
Component:	grubby	Assignee:	Peter Jones <pjones>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	30	CC:	fmartine, pjones
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:	2020-05-07 10:03:16 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 Alan Jenkins 2019-07-01 10:10:55 UTC

Description of problem:

"man grubby" says grubby is "only intended to be called from shell scripts which can get it right".  But grubby is now the official way to change the boot options.


Expected results:

In an ideal world, "man grubby" should gain a helpful EXAMPLES section.

It should also not tell users that they are wrong to run grubby manually.  Unless my information is wrong, and there is a better way?

My information comes from the official Fedora Magazine:

https://fedoramagazine.org/setting-kernel-command-line-arguments-with-fedora-30/


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

How reproducible:
always


Steps to Reproduce:
1. Remember vaguely that "grubby" is the way to update boot options.  Run "man grubby".
2. Read through to the end, hoping for some friendly advice.

Actual results:

"
BUGS

The  command  line  syntax  is  more than a little baroque. This probably won't be fixed *** as grubby is only intended to be called from shell scripts which can get it right ***.
"

Comment 1 Ben Cotton 2020-04-30 21:39:32 UTC

This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
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 '30'.

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 30 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.

Comment 2 Javier Martinez Canillas 2020-05-07 10:03:16 UTC

This was fixed in Rawhide. I'll push for F31 if there's another package update for it.