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.
1. Feature Overview:
Feature Id: [63374]
a. Name of Feature: [6.0 FEAT] Update request for Servicelog
b. Feature Description
libservicelog packages are currently present in RHEL6, but the servicelog package, which uses this
library, is not. This is a request to add the 32-bit version of this package. 64-bit version is
not needed at this time, but might be included as well, to meet Distro partner policy for RHEL6
LI 10-0168
2. Feature Details:
Sponsor: LTC RAS
Architectures:
ppc64
Arch Specificity: purely arch specific code
Affects Kernel Modules: No
Delivery Mechanism: Direct from Community
Category: system management
Request Type: Toolchain - Enhancement from Upstream
d. Upstream Acceptance: No Code Required
Sponsor Priority P2
f. Severity: high
IBM Confidential: No
Code Contribution: IBM code
g. Component Version Target:
---
3. Business Case
Some third party applications, such as IBM Director, require servicelog in order to access and
modify system events, such as hardware errors or maintenance such as adapter replacements.
Servicelog is essential for the smooth management of a Power server, using Director.
4. Primary contact at Red Hat:
John Jarvis
jjarvis
5. Primary contacts at Partner:
Project Management Contact:
Michael W. Wortman, wortman.com
Technical contact(s):
NAREN A. DEVAIAH, naren.devaiah.com
=Comment: #1=================================================
BRAD PETERS <bpeters@linux.vnet.ibm.com> -
Request for servicelog update from current, validated version (1.0.1) to latest available, 1.1.7,
available from [1].
v1.1.x introduced a merged API, combining that of the 0.2.9 and 1.0 API's. This merged API was
requested by IBM Director, and in effect the 1.1.x version is required by all RHEL6 customers who
will be using IBM Director.
[1]: http://sourceforge.net/projects/linux-diag/files/servicelog/1.1/servicelog-1.1.7.tar.gz/download
------- Comment From bpeters.ibm.com 2010-06-09 11:12 EDT-------
Looks good in snapshot 6
Comment 12Alexander Todorov
2010-08-20 18:23:00 UTC
[root@ibm-x3950m2-02 6]# pwd
/mnt/redhat/rel-eng/RHEL6.0-20100818.0/6
[root@ibm-x3950m2-02 6]# find -name "servicelog*"
./Server/source/SRPMS/servicelog-1.1.7-2.el6.src.rpm
./Server/ppc64/os/Packages/servicelog-1.1.7-2.el6.ppc64.rpm
./Server/ppc64/debug/servicelog-debuginfo-1.1.7-2.el6.ppc64.rpm
./source/SRPMS/servicelog-1.1.7-2.el6.src.rpm
See also comment #11. Moving to VERIFIED.
Comment 13releng-rhel@redhat.com
2010-11-10 22:08:13 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.