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:
Hi,
after an openstack minor upgrade (so also resource-agents package has been updated)
pcs cluster became unable to configure a VIP on a specific interface:
pacemaker/pacemaker.log:Oct 11 09:39:46 IPaddr2(ip-172.16.221.35)[533457]: ERROR: Unable to find nic or netmask.
pacemaker/pacemaker.log:Oct 11 09:39:46 IPaddr2(ip-172.16.221.35)[533457]: WARNING: [findif] failed
---
Operation start for ip-172.16.221.35 (ocf:heartbeat:IPaddr2) returned: 'error' (1)
[....]
+++ 13:57:31: findif:220: ip -o -f inet route list match 172.16.221.35/32 scope link
+++ 13:57:31: findif:220: awk 'BEGIN{best=0} /\// { mask=$1; sub(".*/", "", mask); if( int(mask)>=best ) { best=int(mask); best_ln=$0; } } END{print best_ln}'
++ 13:57:31: findif:220: set --
++ 13:57:31: findif:222: '[' 0 = 0 ']'
++ 13:57:31: findif:223: case $OCF_RESKEY_ip in
++ 13:57:31: findif:223: case $OCF_RESKEY_ip in
++ 13:57:31: findif:229: '[' -z '' -o -z 32 ']'
++ 13:57:31: findif:230: '[' 0 = 0 ']' <---- There was nothing returned from "ip" command so length is 0.
++ 13:57:31: findif:231: ocf_log err 'Unable to find nic or netmask.'
[....]
++ 13:57:31: hadate:175: date '+%b %d %T '
+ 13:57:31: __ha_log:250: echo 'IPaddr2(ip-172.16.221.35)[176579]: Oct' 13 13:57:31 'ERROR: [findif] failed'
+ 13:57:31: ip_init:537: exit 1
---
After some investigations with cluster-ha and networking sbr, it turned out that the script findif.sh [1] used by the cluster to check on which nic the VIP has to be configured, doesn't get any output because the route belonging to the VIP's network is in a different routing table from the default one (which is a deliberate choice):
IP CONFIGURED ON vlan10 interfcace:
$ip_addr
...
52: vlan10 inet 172.16.221.38/27 brd 172.16.221.63 scope global vlan10\ valid_lft forever preferred_lft forever
...
COMMAND ISSUED BY SCRIPT (semplified)
ip -o -f inet route list match 172.16.221.35/32 scope link <=== NO OUTPUT
ROUTE BELONGING TO VIP's NETWORK THAT SHOULD MATCH
$ grep "^172.16" ip_route_show_table_all
172.16.221.32/27 dev vlan10 table public scope link <=== is in table public
We managed to get this work by updating the resource specifying the nic name:
pcs resource update ip-172.16.221.35 nic=vlan10
But we'd like to understand if there's another way to have this working, considering that it seems it was working before the update.
[1]http://opengrok.brq.redhat.com/source/xref/RHEL-8/resource-agents-sap/4.1.1/30.el8/ClusterLabs-resource-agents-e711383f/heartbeat/findif.sh#230
Version-Release number of selected component (if applicable):
rhel 8.4
resource-agents.x86_64 4.1.1-90.el8_4.11
How reproducible:
on customer environment
Steps to Reproduce:
1.
2.
3.
Actual results:
cluster fails to configure vip
Expected results:
cluster succeed in configuring VIP
Additional info:
Comment 6RHEL Program Management
2023-09-22 19:48:55 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 7RHEL Program Management
2023-09-22 19:50:56 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Description of problem: Hi, after an openstack minor upgrade (so also resource-agents package has been updated) pcs cluster became unable to configure a VIP on a specific interface: pacemaker/pacemaker.log:Oct 11 09:39:46 IPaddr2(ip-172.16.221.35)[533457]: ERROR: Unable to find nic or netmask. pacemaker/pacemaker.log:Oct 11 09:39:46 IPaddr2(ip-172.16.221.35)[533457]: WARNING: [findif] failed --- Operation start for ip-172.16.221.35 (ocf:heartbeat:IPaddr2) returned: 'error' (1) [....] +++ 13:57:31: findif:220: ip -o -f inet route list match 172.16.221.35/32 scope link +++ 13:57:31: findif:220: awk 'BEGIN{best=0} /\// { mask=$1; sub(".*/", "", mask); if( int(mask)>=best ) { best=int(mask); best_ln=$0; } } END{print best_ln}' ++ 13:57:31: findif:220: set -- ++ 13:57:31: findif:222: '[' 0 = 0 ']' ++ 13:57:31: findif:223: case $OCF_RESKEY_ip in ++ 13:57:31: findif:223: case $OCF_RESKEY_ip in ++ 13:57:31: findif:229: '[' -z '' -o -z 32 ']' ++ 13:57:31: findif:230: '[' 0 = 0 ']' <---- There was nothing returned from "ip" command so length is 0. ++ 13:57:31: findif:231: ocf_log err 'Unable to find nic or netmask.' [....] ++ 13:57:31: hadate:175: date '+%b %d %T ' + 13:57:31: __ha_log:250: echo 'IPaddr2(ip-172.16.221.35)[176579]: Oct' 13 13:57:31 'ERROR: [findif] failed' + 13:57:31: ip_init:537: exit 1 --- After some investigations with cluster-ha and networking sbr, it turned out that the script findif.sh [1] used by the cluster to check on which nic the VIP has to be configured, doesn't get any output because the route belonging to the VIP's network is in a different routing table from the default one (which is a deliberate choice): IP CONFIGURED ON vlan10 interfcace: $ip_addr ... 52: vlan10 inet 172.16.221.38/27 brd 172.16.221.63 scope global vlan10\ valid_lft forever preferred_lft forever ... COMMAND ISSUED BY SCRIPT (semplified) ip -o -f inet route list match 172.16.221.35/32 scope link <=== NO OUTPUT ROUTE BELONGING TO VIP's NETWORK THAT SHOULD MATCH $ grep "^172.16" ip_route_show_table_all 172.16.221.32/27 dev vlan10 table public scope link <=== is in table public We managed to get this work by updating the resource specifying the nic name: pcs resource update ip-172.16.221.35 nic=vlan10 But we'd like to understand if there's another way to have this working, considering that it seems it was working before the update. [1]http://opengrok.brq.redhat.com/source/xref/RHEL-8/resource-agents-sap/4.1.1/30.el8/ClusterLabs-resource-agents-e711383f/heartbeat/findif.sh#230 Version-Release number of selected component (if applicable): rhel 8.4 resource-agents.x86_64 4.1.1-90.el8_4.11 How reproducible: on customer environment Steps to Reproduce: 1. 2. 3. Actual results: cluster fails to configure vip Expected results: cluster succeed in configuring VIP Additional info: