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: IPaddr2 resource's monitor op randomly receives this message
Aug 21 06:21:25 hostname lrmd[PID]: notice: IPresource_monitor_60000:2389:stderr [ Cannot send dump request: Connection refused ]
Aug 21 06:21:25 hostname crmd[PID]: notice: hostname-IPresource_monitor_60000:2074 [ Cannot send dump request: Connection refused\n ]
We believe the above happens when the resource agent executes this code:
local iface="`$IP2UTIL -o -f $FAMILY addr show \
| grep "\ $ipaddr/$netmask" \
| cut -d ' ' -f2 \
| grep -v '^ipsec[0-9][0-9]*$'`"
resulting in the said 'ip -o -f inet addr show' command.
Networking SEG confirmed that the netlink protocol, on which ip command relies, is not 100% reliable, and that a single failure from the ip command should not be seen as fatal.
This happens with at least bonding mode 'round robin' and 'xor' and is not specific to a node or IP resource -- all nodes experience that, and all IP resources experience that, in a random fashion. We have not seen any problematic behaviour concerning the NIC these IPs are attached to.
What we are asking for here is a check that accepts X failure(s) from the said 'ip -o -f inet addr show' command and results in a failed monitor check after it receives X+1 failures from the 'ip' command. Where X is at least 1.
In other words, the monitor action should only fail after second (third..nth) failure obtained from netlink protocol via the 'ip' command.
Version-Release number of selected component (if applicable):
resource-agents-3.9.5-54.el7.x86_64
kernel-3.10.0-327.el7.x86_64
pacemaker-1.1.13-10.el7.x86_64
How reproducible:
Always -- only one check is performed and if this one fails, monitor op returns failure.
The failure itself is random and depends on netlink protocol.
Steps to Reproduce:
1. Set up an IPaddr2 resource
Actual results:
One check testing the IP is performed and if this one fails, monitor op returns failure.
Expected results:
One or more failure(s) is(are) accepted from the 'ip' command. A single failure from the 'ip' command should not result in monitor op returning failure.
Additional info:
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-2018:3278
Description of problem: IPaddr2 resource's monitor op randomly receives this message Aug 21 06:21:25 hostname lrmd[PID]: notice: IPresource_monitor_60000:2389:stderr [ Cannot send dump request: Connection refused ] Aug 21 06:21:25 hostname crmd[PID]: notice: hostname-IPresource_monitor_60000:2074 [ Cannot send dump request: Connection refused\n ] We believe the above happens when the resource agent executes this code: local iface="`$IP2UTIL -o -f $FAMILY addr show \ | grep "\ $ipaddr/$netmask" \ | cut -d ' ' -f2 \ | grep -v '^ipsec[0-9][0-9]*$'`" resulting in the said 'ip -o -f inet addr show' command. Networking SEG confirmed that the netlink protocol, on which ip command relies, is not 100% reliable, and that a single failure from the ip command should not be seen as fatal. This happens with at least bonding mode 'round robin' and 'xor' and is not specific to a node or IP resource -- all nodes experience that, and all IP resources experience that, in a random fashion. We have not seen any problematic behaviour concerning the NIC these IPs are attached to. What we are asking for here is a check that accepts X failure(s) from the said 'ip -o -f inet addr show' command and results in a failed monitor check after it receives X+1 failures from the 'ip' command. Where X is at least 1. In other words, the monitor action should only fail after second (third..nth) failure obtained from netlink protocol via the 'ip' command. Version-Release number of selected component (if applicable): resource-agents-3.9.5-54.el7.x86_64 kernel-3.10.0-327.el7.x86_64 pacemaker-1.1.13-10.el7.x86_64 How reproducible: Always -- only one check is performed and if this one fails, monitor op returns failure. The failure itself is random and depends on netlink protocol. Steps to Reproduce: 1. Set up an IPaddr2 resource Actual results: One check testing the IP is performed and if this one fails, monitor op returns failure. Expected results: One or more failure(s) is(are) accepted from the 'ip' command. A single failure from the 'ip' command should not result in monitor op returning failure. Additional info: