[Sblim-issues] [ sblim-Bugs-3547978 ] Associators method fails to handle name with spaces

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Bugs item #3547978, was opened at 2012-07-24 11:11
Message generated for change (Comment added) made by hellerda
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=712784&aid=3547978&group_id=128809

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Java Client (JSR48)
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: hoai nguyen (nguyener)
Assigned to: Dave Blaschke (blaschke-oss)
Summary: Associators method fails to handle name with spaces

Initial Comment:
1. On a KVM server, create a storage pool with spaces (like Hoai Test StoragePool)
2. get the object path for KVM_AllocationCapabilities of this pool (c3rh6.kirkland.ibm.com:15988/root/virt:KVM_AllocationCapabilities.InstanceID="DiskPool/Hoai Test StoragePool")
3. Get associators for the above object

Errror:

WBEMException: CIM_ERR_NOT_FOUND (Storage pool `Hoai' not found: Storage pool not found: no pool with matching name 'Hoai') 

It seems the pool's name get chopped of at the first space

----------------------------------------------------------------------

Comment By: Dave Heller (hellerda)
Date: 2012-07-30 13:38

Message:
Nevertheless, it appears unlikely to be a client-side issue.  I still
suspect the provider because the CIMOM is returning a NOT_FOUND as opposed
to some other internal error.  Can you check with Sharad if there could
perhaps be a similar bug in a different module?  Also, what is the CIMOM on
your system?

----------------------------------------------------------------------

Comment By: hoai nguyen (nguyener)
Date: 2012-07-30 13:08

Message:
Hi,
I tested the query with libvirt-cim-0.6.1-1.el6.x86_64 (the private buid by
Sharad) and found the problem still exists

----------------------------------------------------------------------

Comment By: Dave Heller (hellerda)
Date: 2012-07-27 09:58

Message:
Clearly this problem is not related to Java CIM client.

I was able to reproduce this on a system running some older KVMPA code,
using either wbemcli or cimcli.  So the problem is likely in the CIMOM or
the provider.  On my system the CIMOM is Openpegasus 2.11.1 and the
libvirt-cim provider is v0.5.14.

I see the following patch for libvirt-cim v0.5.15.  If your provider is
older, suggest you try this patch:
https://www.redhat.com/archives/libvirt-cim/2011-October/msg00009.html

----------------------------------------------------------------------

Comment By: Dave Blaschke (blaschke-oss)
Date: 2012-07-25 19:38

Message:
So the key is the following key (sorry about the play on words):

<KEYBINDING NAME="InstanceID"><KEYVALUE VALUETYPE="string">DiskPool/hoai
test pool</KEYVALUE></KEYBINDING>

The Java CIM Client is sending the key's value out with the spaces
included, so the question becomes, why isn't the CIMOM/provider handling it
properly?  I'd ask the provider first...

----------------------------------------------------------------------

Comment By: hoai nguyen (nguyener)
Date: 2012-07-25 09:22

Message:
[root@c3dev ~]# wbemcli ain -ac CIM_SettingsDefineCapabilities
'http://root:in5...@c3...:15988/root/virt:KVM_AllocationCapabilities.InstanceID="DiskPool/hoai
test pool"' -dx
To server: <?xml version="1.0" encoding="utf-8" ?>
<CIM CIMVERSION="2.0" DTDVERSION="2.0">
<MESSAGE ID="4711" PROTOCOLVERSION="1.0"><SIMPLEREQ><IMETHODCALL
NAME="AssociatorNames"><LOCALNAMESPACEPATH><NAMESPACE
NAME="root"></NAMESPACE><NAMESPACE
NAME="virt"></NAMESPACE></LOCALNAMESPACEPATH>
<IPARAMVALUE NAME="ObjectName"><INSTANCENAME
CLASSNAME="KVM_AllocationCapabilities"><KEYBINDING
NAME="InstanceID"><KEYVALUE VALUETYPE="string">DiskPool/hoai test
pool</KEYVALUE></KEYBINDING></INSTANCENAME></IPARAMVALUE>
<IPARAMVALUE NAME="AssocClass"><CLASSNAME
NAME="CIM_SettingsDefineCapabilities"/></IPARAMVALUE>
</IMETHODCALL></SIMPLEREQ>
</MESSAGE></CIM>
From server: Content-Type: application/xml; charset="utf-8"
From server: content-length: 0000000379
From server: CIMOperation: MethodResponse
From server: <?xml version="1.0" encoding="utf-8" ?>
<CIM CIMVERSION="2.0" DTDVERSION="2.0">
<MESSAGE ID="4711" PROTOCOLVERSION="1.0">
<SIMPLERSP>
<IMETHODRESPONSE NAME="AssociatorNames">
<ERROR CODE="6" DESCRIPTION="CIM_ERR_NOT_FOUND: Storage pool `hoai&apos;
not found: Storage pool not found: no pool with matching name
&apos;hoai&apos;"/></IMETHODRESPONSE>
</SIMPLERSP>
</MESSAGE>
</CIM>

*
* wbemcli: Cim: (6) CIM_ERR_NOT_FOUND: Storage pool `hoai' not found:
Storage pool not found: no pool with matching name 'hoai'
*
[root@c3dev ~]#

----------------------------------------------------------------------

Comment By: Dave Blaschke (blaschke-oss)
Date: 2012-07-25 05:36

Message:
Please enable CIM-XML tracing and capture the outbound HTTP request for the
associators call.  If the VALUE element for the InstanceID key contains
spaces ("DiskPool/Hoai Test StoragePool") then this is almost certainly a
CIMOM/provider issue.  If the key has already been truncated
("DiskPool/Hoai") then this is a Java CIM Client issue.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=712784&aid=3547978&group_id=128809