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:
Version-Release number of selected component (if applicable):
fence-agents-3.1.5-8.el6
How reproducible:
always
Steps to Reproduce:
1. get a fresh RHEL-6.2 machine
2. log as root in via ssh
3. yum -y install audit cman cmirror corosync fence-agents grep initscripts kmod-cmirror libselinux libselinux-utils luci lvm2-cluster mktemp NetworkManager openais policycoreutils rgmanager ricci sed selinux-policy selinux-policy-targeted setools setools-console
Actual results (seen on i386 machine):
Installing : fence-agents-3.1.5-8.el6.i686 29/41
Non-fatal <unknown> scriptlet failure in rpm package fence-agents-3.1.5-8.el6.i686
warning: %triggerin(fence-agents-3.1.5-8.el6.i686) scriptlet failed, exit status 1
Actual results (seen on x86_64 machine):
Installing : fence-agents-3.1.5-8.el6.x86_64 35/41
Non-fatal <unknown> scriptlet failure in rpm package fence-agents-3.1.5-8.el6.x86_64
warning: %triggerin(fence-agents-3.1.5-8.el6.x86_64) scriptlet failed, exit status 1
Expected results:
* no scriptlet failures
Comment 3Fabio Massimo Di Nitto
2011-09-20 04:47:04 UTC
Milos,
I spoke to some rpm/yum guys.
The %triggerin section is executed by some other packages when fence-agents is installed/updated/removed and it's not a bug in fence-agents itself.
As far as I know the only package that does trigger on fence-agents is kdump-tools (or kdump-utils?).
Can you please check if kdump was installed on the system at the time fence-agents was being installed?
Your theory seems to be right. kexec-tools package (which contains kdump) was already installed on the machine when I got it from inventory (before I executed the yum command).
Comment 6Fabio Massimo Di Nitto
2011-09-20 06:56:17 UTC
(In reply to comment #5)
> Your theory seems to be right. kexec-tools package (which contains kdump) was
> already installed on the machine when I got it from inventory (before I
> executed the yum command).
I am also testing this locally now, but could you be so kind to do a counter test by removing kexec-tools from the installation before installing fence-agents?
Thanks!
Comment 7Fabio Massimo Di Nitto
2011-09-20 07:03:21 UTC
OK i have been able to reproduce the problem locally:
rpm -e --nodeps fence-agents
yum install kexec-tools
yum install fence-agents
Running Transaction
Installing : fence-agents-3.1.5-9.el6.x86_64 1/1
Non-fatal <unknown> scriptlet failure in rpm package fence-agents-3.1.5-9.el6.x86_64
warning: %triggerin(fence-agents-3.1.5-9.el6.x86_64) scriptlet failed, exit status 1
Note that I did not configure kexec-tools, but merely installed the package.
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.
http://rhn.redhat.com/errata/RHSA-2011-1532.html