Bug 463847

Summary:	[LTC 6.0 FEAT] 201641:Update SBLIM Java CIM Client to 1.3.6 or later
Product:	Red Hat Enterprise Linux 6	Reporter:	IBM Bug Proxy <bugproxy>
Component:	sblim-cim-client	Assignee:	Vitezslav Crhonek <vcrhonek>
Status:	CLOSED CURRENTRELEASE	QA Contact:	qe-baseos-daemons
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0	CC:	atodorov, cward, dgregor, ejratl, rvokal, snagar, ykopkova
Target Milestone:	alpha	Keywords:	FutureFeature, OtherQA
Target Release:	6.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	sblim-cim-client-1.3.9.1-1.el6	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-11-10 22:20:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	356741, 554559

Description IBM Bug Proxy 2008-09-24 21:01:39 UTC

=Comment: #0=================================================
Emily J. Ratliff <emilyr.com> - 2008-09-24 13:53 EDT
1. Feature Overview:
Feature Id:	[201641]
a. Name of Feature:	Update SBLIM Java CIM Client to 1.3.6 or later
b. Feature Description
Update the SBLIM Java CIM Client from version 1.3.3 (RHEL5.2) to 1.3.6 to pick up latest bug fixes
(15+) and IPv6 support

2. Feature Details:
Sponsor:	LTC Systems Mgt
Architectures:
x86
x86_64
ppc64
s390 native
s390 compat
s390x

Arch Specificity: Purely Common Code
Delivery Mechanism: Direct from community
Category:	Systems management
Request Type:	Package - Feature from Upstream
d. Upstream Acceptance:	Accepted
Sponsor Priority	2
f. Severity: Medium
IBM Confidential:	no
Code Contribution:	IBM code
g. Component Version Target:	Information on the SBLIM Java CIM client 1.3.6 is available at
http://sourceforge.net/forum/forum.php?forum_id=835166  Code is available for download at
http://sourceforge.net/project/showfiles.php?group_id=128809&package_id=164895

3. Business Case
Customer satisfaction - inclusion of the latest fixes/enhancements will improve product
functionality and reliability.  In addition to several critical bug fixes since version 1.3.3,
version 1.3.6 adds IPv6 support to the CIM Client and includes a new IPv6-ready SLP client.

4. Primary contact at Red Hat: 
John Jarvis
jjarvis

5. Primary contacts at Partner:
Project Management Contact:
Sarah Wright, sarahw.com, 503-578-5145

Technical contact(s):

Dave Blaschke, blaschke.com

IBM Manager:
Jeffrey Heroux, heroux.com

Comment 1 IBM Bug Proxy 2009-02-27 21:30:50 UTC

The minimum version (1.3.6) mentioned in this bug is now two releases behind the current version (1.3.8).  Please take the current version if at all possible in order to include all the latest fixes, it was released in December 2008.  All versions can be downloaded here:

http://sourceforge.net/project/showfiles.php?group_id=128809&package_id=164895

Comment 2 IBM Bug Proxy 2009-02-28 16:50:26 UTC

Changing back

Comment 3 IBM Bug Proxy 2009-08-06 16:10:51 UTC

------- Comment From blaschke.com 2009-08-06 12:05 EDT-------
Please include version 1.3.9.1 with RHEL6. It is identical to 1.3.8 except that the license has changed from CPL to EPL so that all SBLIM projects have the same license, plus it includes a critical fix that allows the client to handle CIM errors returned from OpenPegasus 2.9.

Comment 6 releng-rhel@redhat.com 2009-12-16 21:52:03 UTC

Fixed in 'sblim-cim-client-1.3.9.1-1.el6'. 'sblim-cim-client-1.3.9.1-1.el6' included in compose 'RHEL6.0-20091216.nightly'.
Moving to ON_QA.

Comment 7 IBM Bug Proxy 2010-05-24 17:31:15 UTC

------- Comment From blaschke.com 2010-05-24 13:21 EDT-------
Found sblim-cim-client-1.3.9.1-1.el6.noarch.rpm

Comment 8 IBM Bug Proxy 2010-05-25 23:30:54 UTC

------- Comment From blaschke.com 2010-05-25 19:27 EDT-------
FVT of 1.3.9.1 jar executed 100% (2179/2179)

Comment 9 Alexander Todorov 2010-08-25 14:25:43 UTC

VERIFIED par comments #5-#8.

Comment 10 releng-rhel@redhat.com 2010-11-10 22:20: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.