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 1470819[details]
Modified script; enters 0 in the OID fields left blank by the sample script.
Description of problem:
The /usr/share/pacemaker/alerts/alert_snmp.sh.sample file for using Pacemaker Alerts is not consistent with PACEMAKER-MIB (/usr/share/snmp/mibs/PCMK-MIB.txt).
Of the three cases:
- node
- fencing
- resource
Only the resource type sends all the OIDs specified in PACEMAKER-MIB. The trapsink expects all the OID fields to be available in every case, so the lack of fields in the node and fencing types is an issue.
Version-Release number of selected component (if applicable):
pacemaker-1.1.16-12.el7_4.7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Configure alerts using the sample script in accordance with this guidance: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/high_availability_add-on_reference/index#s1-alerts-HAAR
2. Test all three types (node, fencing, resource)
3. Observe OIDs of each type
Actual results:
Only the resource type has all the fields available.
Expected results:
All three types have all the fields available, and conforms to PACEMAKER-MIB.
Additional info:
The attached alert_snmp.sh file has been adjusted to enter 0 in the OID fields that are currently left blank by the sample script; it is currently being used by Vodafone.
The sample alert agents are provided as examples, and are not directly supported, so the user is correct to modify it to suit their needs. The proposed change makes sense; we can incorporate that into the sample, targeted for the 7.7 release.
The proposed sample script will use 2147483647 (the maximum Integer32 value) for unused numeric OIDs and "n/a" for unused string OIDs. These values are user-configurable via the new trap_ignore_int32 and trap_ignore_string parameters.
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-2019:2129