Bug 728157
Summary: | lvrename verb: failed to recognize --force option | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Max Benenson <mbenenso> |
Component: | lvm2 | Assignee: | Zdenek Kabelac <zkabelac> |
Status: | CLOSED ERRATA | QA Contact: | Corey Marthaler <cmarthal> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.1 | CC: | agk, dwysocha, heinzm, jbrassow, mbroz, prajnoha, prockai, thornber, zkabelac |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | lvm2-2.02.86-1.el6 | Doc Type: | Bug Fix |
Doc Text: |
Unsupported option --force has been removed from lvrename manpage.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2011-12-06 16:59:33 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
Max Benenson
2011-08-04 08:47:14 UTC
Option --force has been removed from lvrename man page: https://www.redhat.com/archives/lvm-devel/2011-August/msg00011.html Also missing new line in help text for lvrename has been fixed: https://www.redhat.com/archives/lvm-devel/2011-August/msg00010.html Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Unsupported option --force has been removed from lvrename manpage. Adding QA ack for 6.2. Based on comment #0, a definitive reproducer for this defect exists. Verified that the --force option is no longer in the lvrename man page. 2.6.32-193.el6.x86_64 lvm2-2.02.87-1.el6 BUILT: Fri Aug 12 06:11:57 CDT 2011 lvm2-libs-2.02.87-1.el6 BUILT: Fri Aug 12 06:11:57 CDT 2011 lvm2-cluster-2.02.87-1.el6 BUILT: Fri Aug 12 06:11:57 CDT 2011 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. http://rhn.redhat.com/errata/RHBA-2011-1522.html |