Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Passing a compressed IPv6 address by running
pcs resource create ipv6 ocf:heartbeat:IPaddr2 \
ip=2001:db8:c1234:5::107e:c0a8:2e04 cidr_netmask=96 \
op monitor interval=60s
succeeds at the first glance but then poorly fails to ever bring up this
pacemaker resource, it just fails and leads to
Failed Actions:
[…] exitreason='run_send_ua failed.', […]
And /var/log/messages also provides some errors regarding this (I stripped
the leading date and hostname in the log entries below):
IPaddr2(ipv6_tux)[853]: INFO: Adding inet6 address 2001:db8:c1234:5::107e:c0a8:2e04/96 to device ens192 (with preferred_lft forever)
IPaddr2(ipv6_tux)[853]: INFO: /usr/libexec/heartbeat/send_ua -i 200 -c 5 2001:db8:c1234:5::107e:c0a8:2e04 96 ens192
IPaddr2(ipv6_tux)[1359]: ERROR: Failed to add 2001:db8:c1234:5::107e:c0a8:2e04
lrmd[27797]: notice: ipv6_start_0:1359:stderr [ ocf-exit-reason:Failed to add 2001:db8:c1234:5::107e:c0a8:2e04 ]
and
kernel: IPv6: ens192: IPv6 duplicate address 2001:db8:c1234:5:0:107e:c0a8:2e04 detected!
IPaddr2(ipv6_tux)[31739]: ERROR: IPv6 address collision 2001:db8:c1234:5::107e:c0a8:2e04 [DAD]
IPaddr2(ipv6_tux)[31739]: ERROR: run_send_ua failed.
If I however pass a non-compressed IPv6 address by running
pcs resource update ipv6 \
ip=2001:db8:c1234:5:0:107e:c0a8:2e04 cidr_netmask=96
it succeeds not only at the first glance, but really works without any IPv6
DAD issues.
Note: IPv6 address has been obsfuscated for this RHBZ using an IPv6 address
according to RFC 5737 (documentation range).
Version-Release number of selected component (if applicable):
resource-agents-3.9.5-105.el7_4.3.x86_64
How reproducible:
See above.
Actual results:
Passing compressed IPv6 address to ocf::heartbeat:IPaddr2 leads to IPv6 DAD
trouble.
Expected results:
Passing compressed IPv6 address to ocf::heartbeat:IPaddr2 should be either
not possible (lead to a failure) or should not lead to IPv6 DAD trouble by
expanding the IPv6 address itself before using it (second preferred to be a
bit more admin friendly).
(In reply to Oyvind Albrigtsen from comment #3)
> :c1234: there can only be 4 hexadecimal digits per group.
Sorry, this happened due to obsfuscation for this report. Use :c123: or
:1234: to reproduce this issue.
Comment 5Oyvind Albrigtsen
2018-01-16 15:01:50 UTC
Oh.
It seems like the issue is due to ":: is not used to shorten just a single 0 field.", so "ip a" shows your address with :0:, but if you replace :0:0: or more with :: "ip a" shows it as expected.
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/RHBA-2020:1067
Description of problem: Passing a compressed IPv6 address by running pcs resource create ipv6 ocf:heartbeat:IPaddr2 \ ip=2001:db8:c1234:5::107e:c0a8:2e04 cidr_netmask=96 \ op monitor interval=60s succeeds at the first glance but then poorly fails to ever bring up this pacemaker resource, it just fails and leads to Failed Actions: […] exitreason='run_send_ua failed.', […] And /var/log/messages also provides some errors regarding this (I stripped the leading date and hostname in the log entries below): IPaddr2(ipv6_tux)[853]: INFO: Adding inet6 address 2001:db8:c1234:5::107e:c0a8:2e04/96 to device ens192 (with preferred_lft forever) IPaddr2(ipv6_tux)[853]: INFO: /usr/libexec/heartbeat/send_ua -i 200 -c 5 2001:db8:c1234:5::107e:c0a8:2e04 96 ens192 IPaddr2(ipv6_tux)[1359]: ERROR: Failed to add 2001:db8:c1234:5::107e:c0a8:2e04 lrmd[27797]: notice: ipv6_start_0:1359:stderr [ ocf-exit-reason:Failed to add 2001:db8:c1234:5::107e:c0a8:2e04 ] and kernel: IPv6: ens192: IPv6 duplicate address 2001:db8:c1234:5:0:107e:c0a8:2e04 detected! IPaddr2(ipv6_tux)[31739]: ERROR: IPv6 address collision 2001:db8:c1234:5::107e:c0a8:2e04 [DAD] IPaddr2(ipv6_tux)[31739]: ERROR: run_send_ua failed. If I however pass a non-compressed IPv6 address by running pcs resource update ipv6 \ ip=2001:db8:c1234:5:0:107e:c0a8:2e04 cidr_netmask=96 it succeeds not only at the first glance, but really works without any IPv6 DAD issues. Note: IPv6 address has been obsfuscated for this RHBZ using an IPv6 address according to RFC 5737 (documentation range). Version-Release number of selected component (if applicable): resource-agents-3.9.5-105.el7_4.3.x86_64 How reproducible: See above. Actual results: Passing compressed IPv6 address to ocf::heartbeat:IPaddr2 leads to IPv6 DAD trouble. Expected results: Passing compressed IPv6 address to ocf::heartbeat:IPaddr2 should be either not possible (lead to a failure) or should not lead to IPv6 DAD trouble by expanding the IPv6 address itself before using it (second preferred to be a bit more admin friendly).