Red Hat Bugzilla – Bug 454590
CMPI MI factories that return errors are unsupported
Last modified: 2009-06-20 00:47:38 EDT
Description of problem:
From OpenPegasus bugzilla 7525 at:
"The CMPI spec states that MI factories "may return a NULL pointer indicating
that a particular MI type is not supported, despite the fact that the factory is
found". The current code in src/Pegasus/ProviderManager2/CMPI/CMPIProvider.cpp
does not reflect this condition.
Currently, if any provider MI functions return NULL or set the CMPIStatus output
parameter to anything other than OK, a CIM exception is generated:
CIM_ERR_FAILED: Error initializing CMPI MI SMXProfileRegistration, the
following MI factory function(s) returned an error: _Generic_Create_MethodMI;
This bug causes CMPI providers that return errors as per the CMPI standard to be
unloadable under tog-pegasus.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Partners, this bug should be fixed in the latest RHEL 5.3 Snapshot. We believe that you have some interest in its correct functionality, so we're making a friendly request to send us some testing feedback.
If you have a chance to test it, please share with us your findings. If you have successfully VERIFIED the fix, please add PartnerVerified to the Bugzilla keywords, along with a description of the results. Thanks!
Verified from partners, adding SanityOnly, as I couldn't test this bug.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.