Bug 920763 - CIMOM refuses EmbeddedObject with unknown class
Summary: CIMOM refuses EmbeddedObject with unknown class
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: tog-pegasus
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Vitezslav Crhonek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-12 17:00 UTC by Jan Safranek
Modified: 2014-02-05 19:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 19:54:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jan Safranek 2013-03-12 17:00:08 UTC
I have a CMPI provider for CIM_MethodResult class. It has EmbeddedInstance('CIM_InstMethodCall') property PostCallIndication.

CIM_InstMethodCall class has EmbeddedObject property MethodParameters and description of the property says:

   The parameters of the method, formatted as an EmbeddedObject (with a
   predefined class name of "__MethodParameters". 

Now if I set the MethodParameters property with CIM instance of not-existing "__MethodParameters" class, Pegasus returns CMPI_RC_ERR_NOT_FOUND from src/Pegasus/ProviderManager2/CMPI/CMPI_BrokerEnc.cpp:mbEncNewInstance()

If I try to use "CIM_ManagedElement" as classname of the embedded object just for testing, Pegasus shows correct property, i.e. these EmbeddedInstances and EmbeddedObjects work well for registered classes. 

Problem is that "__MethodParameters" is not registered class and Pegasus does not like it. Would it be possible not to check the class name for EmbeddedObjects? DMTF defined some EmbeddedObject properties with undefined classes, in addition to CIM_InstMethodCall.MethodParameters also e.g. CIM_ConcreteJob.JobInParameters.

Version-Release number of selected component (if applicable):
tog-pegasus-2.12.0-15.fc19

Comment 1 Fedora End Of Life 2013-12-21 12:06:00 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2014-02-05 19:54:29 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.