Bug 520458 - RFE: IPv6 support for fencing agents
RFE: IPv6 support for fencing agents
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: cman (Show other bugs)
5.3
All Linux
low Severity medium
: rc
: ---
Assigned To: Marek Grac
Cluster QE
: FutureFeature, TechPreview
Depends On:
Blocks: 557292 5.5TechNotes-Updates
  Show dependency treegraph
 
Reported: 2009-08-31 11:06 EDT by Marek Grac
Modified: 2016-04-26 09:43 EDT (History)
7 users (show)

See Also:
Fixed In Version: cman-2.0.115-4.el5
Doc Type: Technology Preview
Doc Text:
Cause: attempt to use IPv6 only in cluster Consequences: fence agent doesn't work with IPv6 if IPv4 is enabled Fix: options -4/-6 (inet4_only/inet6_only) use only given protocol Result: fence agents can specify which IP protocol they should use.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-03-30 04:41:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Proposed patch (7.92 KB, patch)
2009-08-31 11:18 EDT, Marek Grac
no flags Details | Diff

  None (edit)
Description Marek Grac 2009-08-31 11:06:34 EDT
Description of problem:

It should be possible to force usage of IPv4/IPv6 in fencing agents.
Comment 1 Marek Grac 2009-08-31 11:18:35 EDT
Created attachment 359279 [details]
Proposed patch

Updated patch from upstream
Comment 10 Marek Grac 2010-02-12 05:39:37 EST
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:
Cause: attempt to use IPv6 only in cluster
Consequences: fence agent doesn't work with IPv6 if IPv4 is enabled
Fix: options -4/-6 (inet4_only/inet6_only) use only given protocol
Result: fence agents can specify which IP protocol they should use.
Comment 12 errata-xmlrpc 2010-03-30 04:41:34 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0266.html

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