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 1528011 - boom man page shows unquoted --title example
Summary: boom man page shows unquoted --title example
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lvm2
Version: 7.5
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Bryn M. Reeves
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-20 18:47 UTC by Corey Marthaler
Modified: 2021-09-03 12:41 UTC (History)
9 users (show)

Fixed In Version: lvm2-2.02.177-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 15:23:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0853 0 None None None 2018-04-10 15:24:41 UTC

Description Corey Marthaler 2017-12-20 18:47:35 UTC 
Description of problem:

from man boom:
 # boom create --profile 3fc389b --title RHEL7 snapshot --version 3.10-272.el7 --rootlv vg00/lvol0-snap
       Created entry with boot_id a5aef11:

In reality, this wouldn't work:
[root@mckinley-03 ~]# boom create --profile 3fc389b --title RHEL7 snapshot --version 3.10-272.el7 --rootlv snapper/snap1
usage: boom [-h] [-b BOOT_ID] [--boot-dir PATH] [-B SUBVOL]
            [--btrfs-opts OPTS] [--debug DEBUGOPTS] [-e IMG] [-H] [-i IMG]
            [-k PATTERN] [-l IMG] [-L LV] [--lvm-opts OPTS] [-m MACHINE_ID]
            [-n OSNAME] [--nameprefixes] [--noheadings] [-o FIELDS]
            [--os-version OSVERSION] [-O SORTFIELDS] [-I OSVERSIONID]
            [--os-options OPTIONS] [--os-release OSRELEASE] [-p OS_ID]
            [-r ROOT] [-R PATTERN] [--rows] [--separator SEP] [-s OSSHORTNAME]
            [-t TITLE] [-u PATTERN] [-V] [-v VERSION]
            [TYPE] COMMAND [ID]
boom: error: unrecognized arguments: snapshot


Version-Release number of selected component (if applicable):
lvm2-python-boom-0.8.1-5.el7    BUILT: Wed Dec  6 04:15:40 CST 2017
Comment 3 Marian Csontos 2018-02-07 10:27:54 UTC 
Commit: ac24bef071f0cabb4b594c39f92179904365a518
Comment 6 Corey Marthaler 2018-02-07 23:51:24 UTC 
Fix verified in the latest rpms.

       # boom create --profile 3fc389b --title "RHEL7 snapshot" --version 3.10-272.el7 --rootlv vg00/lvol0-snap
       Created entry with boot_id a5aef11:
       title RHEL7 snapshot
       machine-id 611f38fd887d41dea7eb3403b2730a76
       version 3.10-272.el7
       linux /boot/vmlinuz-3.10-272.el7
       initrd /boot/initramfs-3.10-272.el7.img
       options root=/dev/vg00/lvol0-snap ro rd.lvm.lv=vg00/lvol0-snap rhgb quiet




3.10.0-847.el7.x86_64

lvm2-2.02.177-2.el7    BUILT: Wed Feb  7 17:39:26 CET 2018
lvm2-libs-2.02.177-2.el7    BUILT: Wed Feb  7 17:39:26 CET 2018
lvm2-cluster-2.02.177-2.el7    BUILT: Wed Feb  7 17:39:26 CET 2018
lvm2-lockd-2.02.177-2.el7    BUILT: Wed Feb  7 17:39:26 CET 2018
lvm2-python-boom-0.8.3-2.el7    BUILT: Wed Feb  7 17:42:09 CET 2018
cmirror-2.02.177-2.el7    BUILT: Wed Feb  7 17:39:26 CET 2018
device-mapper-1.02.146-2.el7    BUILT: Wed Feb  7 17:39:26 CET 2018
device-mapper-libs-1.02.146-2.el7    BUILT: Wed Feb  7 17:39:26 CET 2018
device-mapper-event-1.02.146-2.el7    BUILT: Wed Feb  7 17:39:26 CET 2018
device-mapper-event-libs-1.02.146-2.el7    BUILT: Wed Feb  7 17:39:26 CET 2018
device-mapper-persistent-data-0.7.3-3.el7    BUILT: Tue Nov 14 12:07:18 CET 2017
Comment 9 errata-xmlrpc 2018-04-10 15:23:49 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/RHEA-2018:0853
Note You need to log in before you can comment on or make changes to this bug.