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 761228 - fence_virt(8) man page section notice error
Summary: fence_virt(8) man page section notice error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: fence-virt
Version: 6.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: 6.3
Assignee: Ryan McCabe
QA Contact: Chris Mackowski
URL:
Whiteboard:
Depends On:
Blocks: 782183 840699
TreeView+ depends on / blocked
 
Reported: 2011-12-07 21:47 UTC by Dustin Black
Modified: 2018-11-29 21:41 UTC (History)
9 users (show)

Fixed In Version: fence-virt-0.2.3-11.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-21 10:24:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0419 0 normal SHIPPED_LIVE fence-virt bug fix and enhancement update 2013-02-20 20:49:42 UTC

Description Dustin Black 2011-12-07 21:47:56 UTC
Description of problem:
In the fence_virt(8) man page, the section "SERIAL/VMCHANNEL PARAMETERS" includes a note:

These parameters are used only when using fence_virt in multicast mode (e.g. by running fence_xvm).

This note is verbatim from the above "MULTICAST PARAMETERS" section, but is erroneous in the "SERIAL/VMCHANNEL PARAMETERS" section, as this section applies in exactly the opposite situation, when NOT running in fence_xvm multicast mode.

Version-Release number of selected component (if applicable):
0.2.1-8.el6.x86_64

Comment 4 RHEL Program Management 2012-07-10 06:39:24 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 7 Ludek Smid 2012-07-11 11:36:13 UTC
This request was erroneously removed from consideration in
Red Hat Enterprise Linux 6.4, which is currently under
development.  This request will be evaluated for inclusion
in Red Hat Enterprise Linux 6.4.

Comment 9 Ryan McCabe 2012-10-08 14:55:51 UTC
commit b35ac70bf29b4137ca30d5cb4a33ad6f7ba00059
Author: Ryan McCabe <rmccabe>
Date:   Mon Oct 8 10:54:25 2012 -0400

    fence_virt: Fix typo in fence_virt(8) man page
    
    Fix the description of when serial/vmchannel parameters are accepted.
    
    Resolves: rhbz#761228
    Signed-off-by: Ryan McCabe <rmccabe>

Comment 13 errata-xmlrpc 2013-02-21 10:24:48 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.

http://rhn.redhat.com/errata/RHBA-2013-0419.html


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