On 10/12/2011 02:01 PM, Gareth S Bestor wrote:
This fix is in tog-pegasus-2.12, so yes you probably have this bug in your version (unless its been patched)
Ideally, the cimom type (sfcb vs pegasus) and version shouldn't matter in most instances, with the excpetion of perhaps actual *new* features, like reliable indications, embeeded instance support, etc... I think having a cimom check in the cimtest suites would be OK for such things. But I dont think adding explicit checks for what are ostensibly occasional bugs in a particular version of a particular packages is a path we really want to go down... (eg this bug popped up only in pegasus 2.10/2.11; this worked back in 2.9 days). Eduardo's testcase is valid; this is just a test that will fail when run against a particular version of (unpatched) pegasus. That should be noted somewhere, but I dont think we necessarily need to 'work around it'...
Indeed, this test case basically tests this functionality to issue a ModifyResourceSettings call with an empty as argument. This bug was reported in pegasus bugzilla[1] and fixed as per version 2.11.1. If the test fails, then it exposes that pegasus bug, which means you need to upgrade your packages. [1] http://bugzilla.openpegasus.org/show_bug.cgi?id=9053 -- Eduardo de Barros Lima Software Engineer, Open Virtualization Linux Technology Center - IBM/Brazil eblima@br.ibm.com