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.
Created attachment 1470004[details]
corosync.log snippet of the failure event
Description of problem:
Now and then we see stonith resource failures e.g.
* s390_ssi-fence1_monitor_60000 on qe-c02-m01 'unknown error' (1): call=26, status=Error, exitreason='',
last-rc-change='Sun Jul 22 23:38:36 2018', queued=0ms, exec=15127ms
Version-Release number of selected component (if applicable):
fence-agents-zvm-4.2.1-4.el7.s390x
How reproducible:
Happens sporadically, sometimes under no test load.
Steps to Reproduce:
1. Set up a cluster on s390x with a fence_zvmip fence agent
Actual results:
Jul 22 23:38:51 [2579] qe-c02-m01.s390.bos.redhat.com stonith-ng: warning: log_action: fence_zvmip[29579] stderr: [ 2018-07-22 23:38:51,496 ERROR: Unable to connect/login to fencing device ]
(See attached log file snippet for the whole event)
Expected results:
No failures.
Additional info:
The SMAPI logs show two successful calls originating from qe-c02-m01 (10.16.106.132) at this point, which suggests it's a problem in the fence agent:
06314 2018-07-22 23:38:38 REQUE DMSRSRQN REQ_ACC VSMREQIN AF_INET 36866 10.16.106.132
06315 2018-07-22 23:38:38 ENTRY DMSRSRQT REQ_INET VSMREQIN
06316 2018-07-22 23:38:38 EXIT DMSRSRQT REQ_INET VSMREQIN 0 0
06317 2018-07-22 23:38:38 REQUE DMSRSRQN REQ_ACC VSMREQIN AF_INET 36868 10.16.106.132
06318 2018-07-22 23:38:38 ENTRY DMSRSRQT REQ_INET VSMREQIN
06319 2018-07-22 23:38:38 EXIT DMSRSRQT REQ_INET VSMREQIN 0 0
(The hypervisor's clock is 13 seconds out so the log entries do match up.)
Comment 4RHEL Program Management
2021-02-15 07:40:49 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Created attachment 1470004 [details] corosync.log snippet of the failure event Description of problem: Now and then we see stonith resource failures e.g. * s390_ssi-fence1_monitor_60000 on qe-c02-m01 'unknown error' (1): call=26, status=Error, exitreason='', last-rc-change='Sun Jul 22 23:38:36 2018', queued=0ms, exec=15127ms Version-Release number of selected component (if applicable): fence-agents-zvm-4.2.1-4.el7.s390x How reproducible: Happens sporadically, sometimes under no test load. Steps to Reproduce: 1. Set up a cluster on s390x with a fence_zvmip fence agent Actual results: Jul 22 23:38:51 [2579] qe-c02-m01.s390.bos.redhat.com stonith-ng: warning: log_action: fence_zvmip[29579] stderr: [ 2018-07-22 23:38:51,496 ERROR: Unable to connect/login to fencing device ] (See attached log file snippet for the whole event) Expected results: No failures. Additional info: The SMAPI logs show two successful calls originating from qe-c02-m01 (10.16.106.132) at this point, which suggests it's a problem in the fence agent: 06314 2018-07-22 23:38:38 REQUE DMSRSRQN REQ_ACC VSMREQIN AF_INET 36866 10.16.106.132 06315 2018-07-22 23:38:38 ENTRY DMSRSRQT REQ_INET VSMREQIN 06316 2018-07-22 23:38:38 EXIT DMSRSRQT REQ_INET VSMREQIN 0 0 06317 2018-07-22 23:38:38 REQUE DMSRSRQN REQ_ACC VSMREQIN AF_INET 36868 10.16.106.132 06318 2018-07-22 23:38:38 ENTRY DMSRSRQT REQ_INET VSMREQIN 06319 2018-07-22 23:38:38 EXIT DMSRSRQT REQ_INET VSMREQIN 0 0 (The hypervisor's clock is 13 seconds out so the log entries do match up.)