RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1168121 - yum fssnapshot manpage description is confusing
Summary: yum fssnapshot manpage description is confusing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: yum
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: Michal Domonkos
QA Contact: Eva Mrakova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-26 08:16 UTC by Karel Srot
Modified: 2016-11-04 05:27 UTC (History)
3 users (show)

Fixed In Version: yum-3.4.3-138.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 05:27:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2397 0 normal SHIPPED_LIVE yum bug fix and enhancement update 2016-11-03 13:55:12 UTC

Description Karel Srot 2014-11-26 08:16:49 UTC
yum manpage is mentioning yum fssnap command (see below) but no such command is listed in yum --help. 

# yum --help | grep fssnap
fssnapshot     Creates filesystem snapshots, or lists/deletes current snapshots.

It seems that both commands work the same way (aliases?) but 
current manpage description is confusing since it suggest sometimes use fssnapshot and sometimes fssnap.

yum-3.4.3-124.el7.noarch

------------------------

       fssnapshot
              This command has a few sub-commands to act on the LVM data of the host, to list snapshots and
              the  create  and remove them. The simplest commands, to display information about the config‐
              ured LVM snapshotable devices, are:

               yum fssnapshot [summary]
               yum fssnapshot list
               yum fssnapshot have-space

              then you can create and delete snapshots using:

               yum fssnap create
               yum fssnap delete <device(s)>

--------------------------------

Comment 5 Michal Domonkos 2016-02-18 12:49:48 UTC
Correct, these two are just aliases for the same command.  We'll fix the man page.

Comment 6 Michal Domonkos 2016-02-18 13:41:48 UTC
Upstream PR:
https://github.com/rpm-software-management/yum/pull/6

Comment 13 errata-xmlrpc 2016-11-04 05:27:51 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://rhn.redhat.com/errata/RHBA-2016-2397.html


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