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.
Bug 999585 - non-fatal systemtap scriptlet failure
Summary: non-fatal systemtap scriptlet failure
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemtap
Version: 7.0
Hardware: ppc64
OS: Linux
medium
medium
Target Milestone: beta
: ---
Assignee: Frank Ch. Eigler
QA Contact: Martin Cermak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-21 15:46 UTC by Miroslav Franc
Modified: 2016-02-01 02:28 UTC (History)
5 users (show)

Fixed In Version: systemtap-2.4-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 09:31:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Miroslav Franc 2013-08-21 15:46:38 UTC
Description of problem:
Systemtap tries to create symlinks in /usr/lib/jvm/*openjdk*/jre/lib/powerpc64, most likely it should be in /usr/lib/jvm/*openjdk*/jre/lib/ppc64.


Version-Release number of selected component (if applicable):
systemtap-runtime-java-2.3-1.el7.ppc64


Steps to Reproduce:
1. yum install systemtap-runtime-java


Actual results:
...
  Installing : systemtap-runtime-java-2.3-1.el7.ppc64                                                                                                                                 1/1 
ln: failed to create symbolic link ‘/usr/lib/jvm/*openjdk*/jre/lib/powerpc64/libHelperSDT_powerpc64.so’: No such file or directory
ln: failed to create symbolic link ‘/usr/lib/jvm/*openjdk*/jre/lib/powerpc64/../ext/HelperSDT.jar’: No such file or directory
warning: %triggerin(systemtap-runtime-java-2.3-1.el7.ppc64) scriptlet failed, exit status 1
Non-fatal <unknown> scriptlet failure in rpm package systemtap-runtime-java-2.3-1.el7.ppc64
...


Expected results:
no scriptlet failure

Comment 1 Frank Ch. Eigler 2013-08-27 14:56:10 UTC
upstream commits 1554f7e, 5a9457fc8

Comment 2 Mark Wielaard 2013-10-04 12:09:56 UTC
(In reply to Frank Ch. Eigler from comment #1)
> upstream commits 1554f7e, 5a9457fc8

That is commits 1553f7e and 5a9457fc8
                   ^

Comment 4 Ludek Smid 2014-06-13 09:31:23 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


Note You need to log in before you can comment on or make changes to this bug.