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 1276699 - [RFE] IPaddr2: Use IPv6 DAD for collision detection
Summary: [RFE] IPaddr2: Use IPv6 DAD for collision detection
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: resource-agents
Version: 7.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Oyvind Albrigtsen
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1191247 1276698
Blocks: 1172231
TreeView+ depends on / blocked
 
Reported: 2015-10-30 14:34 UTC by Oyvind Albrigtsen
Modified: 2016-11-03 23:58 UTC (History)
13 users (show)

Fixed In Version: resource-agents-3.9.5-63.el7
Doc Type: Enhancement
Doc Text:
Clone Of: 1276698
Environment:
Last Closed: 2016-11-03 23:58:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Working patch (1.77 KB, patch)
2015-10-30 14:37 UTC, Oyvind Albrigtsen 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2174 0 normal SHIPPED_LIVE resource-agents bug fix and enhancement update 2016-11-03 13:16:36 UTC

Comment 1 Oyvind Albrigtsen 2015-10-30 14:37:08 UTC 
Created attachment 1087945 [details]
Working patch

Tested and working patch.
Comment 5 Oyvind Albrigtsen 2016-03-01 12:09:44 UTC 
Setup an IPv6 address resource that collides with one on the network:
# pcs resource create IPv6 IPaddr2 ip=XXXX::10

Before:
# rpm -q resource-agents
resource-agents-3.9.5-54.el7_2.6.x86_64
# pcs resource enable IPv6
# tail -f /var/log/pacemaker.log
...
IPaddr2(IPv6)[5109]:    2016/03/01_13:02:28 WARNING: XXXX::10 still has 'tentative' status. (ignored)

After:
# rpm -q resource-agents
resource-agents-3.9.5-63.el7.x86_64
# pcs resource enable IPv6
# tail -f /var/log/pacemaker.log
...
IPaddr2(IPv6)[7572]:	2016/03/01_13:08:24 ERROR: IPv6 address collision XXXX::10 [DAD]
Comment 6 michal novacek 2016-07-27 10:26:23 UTC 
I have verified that DAD is used for ipv6 address collision detection in
resource-agents-3.9.5-73.el6.x86_64

-----

setup:

Have active ipv6 address and stopped cluster resource with the same address.

[root@virt-140 ~]# ping6 -c 2 2620:52:0:2246:1800:ff:fe00:8c
PING 2620:52:0:2246:1800:ff:fe00:8c(2620:52:0:2246:1800:ff:fe00:8c) 56 data bytes
64 bytes from 2620:52:0:2246:1800:ff:fe00:8c: icmp_seq=1 ttl=64 time=0.057 ms
64 bytes from 2620:52:0:2246:1800:ff:fe00:8c: icmp_seq=2 ttl=64 time=0.064 ms

--- 2620:52:0:2246:1800:ff:fe00:8c ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.057/0.060/0.064/0.008 ms

[root@virt-140 ~]# pcs resource show ClusterIP
 Resource: ClusterIP (class=ocf provider=heartbeat type=IPaddr2)
  Attributes: ip=2620:52:0:2246:1800:ff:fe00:8c cidr_netmask=64 
  Meta Attrs: target-role=Stopped 
  Operations: start interval=0s timeout=20s (ClusterIP-start-interval-0s)
              stop interval=0s timeout=20s (ClusterIP-stop-interval-0s)
              monitor interval=10s timeout=20s (ClusterIP-monitor-interval-10s)

[root@virt-140 ~]# pcs status
Cluster name: STSRHTS24626
Last updated: Wed Jul 27 11:32:59 2016          Last change: Wed Jul 27 11:28:54 2016 by root via crm_resource on virt-140
Stack: corosync
Current DC: virt-149 (version 1.1.13-10.el7-44eb2dd) - partition with quorum
4 nodes and 13 resources configured

Online: [ virt-140 virt-148 virt-149 virt-150 ]

Full list of resources:

 fence-virt-140 (stonith:fence_xvm):    Started virt-140
 fence-virt-148 (stonith:fence_xvm):    Started virt-148
 fence-virt-149 (stonith:fence_xvm):    Started virt-149
 fence-virt-150 (stonith:fence_xvm):    Started virt-150
 Clone Set: dlm-clone [dlm]
     Started: [ virt-140 virt-148 virt-149 virt-150 ]
 Clone Set: clvmd-clone [clvmd]
     Started: [ virt-140 virt-148 virt-149 virt-150 ]
 ClusterIP      (ocf::heartbeat:IPaddr2):       (target-role:Stopped) Stopped

PCSD Status:
  virt-140: Online
  virt-148: Online
  virt-149: Online
  virt-150: Online

Daemon Status:
  corosync: active/disabled
  pacemaker: active/disabled
  pcsd: active/enabled

before the fix (resource-agents-3.9.5-54.el7.x86_64)
====================================================

# pcs resource enable ClusterIP
# pcs status | grep ClusterIP
 ClusterIP      (ocf::heartbeat:IPaddr2):       Stopped

# tail /var/log/messages
...
Jul 30 11:39:07 virt-140 IPaddr2(ClusterIP)[4523]: INFO: Adding inet6 address 2620:52:0:2246:1800:ff:fe00:8c/64 to device eth0
Jul 30 11:39:07 virt-140 IPaddr2(ClusterIP)[4523]: INFO: Bringing device eth0 up
>>> Jul 30 11:39:11 virt-140 IPaddr2(ClusterIP)[4523]: WARNING: 2620:52:0:2246:1800:ff:fe00:90 still has 'tentative' status. (ignored)
Jul 30 11:39:11 virt-140 IPaddr2(ClusterIP)[4523]: INFO: /usr/libexec/heartbeat/send_ua -i 200 -c 5 2620:52:0:2246:1800:ff:fe00:8c 64 eth0


after the fix (resource-agents-3.9.5-73.el7.x86_64)
===================================================

# pcs resource enable ClusterIP
# pcs status | grep ClusterIP
 ClusterIP      (ocf::heartbeat:IPaddr2):       Stopped

# tail /var/log/messages
...
Jul 27 11:36:41 virt-150 IPaddr2(ClusterIP)[18826]: INFO: Adding inet6 address 2620:52:0:2246:1800:ff:fe00:8c/64 to device eth0
Jul 27 11:36:41 virt-150 IPaddr2(ClusterIP)[18826]: INFO: Bringing device eth0 up
Jul 27 11:36:41 virt-150 kernel: IPv6: eth0: IPv6 duplicate address 2620:52:0:2246:1800:ff:fe00:8c detected!
>>> Jul 27 11:36:42 virt-150 IPaddr2(ClusterIP)[18826]: ERROR: IPv6 address collision 2620:52:0:2246:1800:ff:fe00:8c [DAD]
Jul 27 11:36:42 virt-150 IPaddr2(ClusterIP)[18826]: ERROR: run_send_ua failed.
Jul 27 11:36:42 virt-150 lrmd[24755]:  notice: ClusterIP_start_0:18826:stderr [ ocf-exit-reason:run_send_ua failed. ]
Jul 27 11:36:42 virt-150 crmd[24758]:  notice: Operation ClusterIP_start_0: unknown error (node=virt-150, call=74, rc=1, cib-update=58, confirmed=true)
Jul 27 11:36:42 virt-150 crmd[24758]:  notice: virt-150-ClusterIP_start_0:74 [ ocf-exit-reason:run_send_ua failed.\n ]
Jul 27 11:36:42 virt-150 IPaddr2(ClusterIP)[18911]: INFO: IP status = no, IP_CIP=
Jul 27 11:36:42 virt-150 crmd[24758]:  notice: Operation ClusterIP_stop_0: ok (node=virt-150, call=75, rc=0, cib-update=59, confirmed=true)
Comment 8 errata-xmlrpc 2016-11-03 23:58:55 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-2174.html
Note You need to log in before you can comment on or make changes to this bug.