Bug 1651673

Summary:	Improve man page for --info option
Product:	Red Hat Enterprise Linux 7	Reporter:	Jan Stodola <jstodola>
Component:	grubby	Assignee:	Bootloader engineering team <bootloader-eng-team>
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	low	Docs Contact:
Priority:	low
Version:	7.6	CC:	bootloader-eng-team, fmartine, release-test-team-automation
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	grubby-8.28-26.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1651672	Environment:
Last Closed:	2019-08-06 13:07:10 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:
Bug Depends On:
Bug Blocks:	1568427, 1670353

Description Jan Stodola 2018-11-20 14:40:07 UTC

+++ This bug was initially created as a clone of Bug #1651672 +++

Description of problem:
man page for grubby's --info option is missing a part of a sentence:

       --info=kernel-path
              Display information on all boot entries which match kernel-path. I

Based on the grubby.8 man file history, the sentence was describing the DEFAULT option argument. Return this part and also describe the ALL option argument, which is also accepted by the --info option.

Version-Release number of selected component (if applicable):
grubby-8.40-29.el8

How reproducible:
always

Steps to Reproduce:
1. man grubby

Actual results:
--info option is not complete, DEFAULT and ALL arguments are not described

Expected results:
DEFAULT and ALL arguments are not described

--- Additional comment from Jan Stodola on 2018-11-20 15:37:08 CET ---

upstream pull request:
https://github.com/rhboot/grubby/pull/43

Comment 1 Jan Stodola 2018-11-20 14:41:50 UTC

Version of the package: grubby-8.28-25.el7

Comment 5 errata-xmlrpc 2019-08-06 13:07:10 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2227