[Libvirt-cim] [PATCH] [TEST] Fix SettingsDefineCapabilities/03_forward_errs.py

[Guo Lian Yun]

libvirt-cim-bounces at redhat.com wrote on 2008-11-14 07:57:14:

> >  > Daisy - did you resolve your problem?  I tested with an F9 rpm 
using
> >  > Pegasus, and this test passed for me.
> >  >
> >  >
> >   This tc passes for Pegasus, but it fails for sfcb.
> >   It expects different error code and description for sfcb and 
Pegasus.
> > 
> >   If I change the expr_valuese from 1) to 2), it passes for sfcb.
> > 
> >   1)
> > expr_values = {
> >    "invalid_instid_keyvalue" : { 'rc' : pywbem.CIM_ERR_FAILED,
> >                                  'desc' : 'Unable to determine\
> >  resource type' },
> >               }
> > 
> >   2)
> > expr_values = {
> >    "invalid_instid_keyvalue" : { 'rc' : pywbem.CIM_ERR_NOT_FOUNG,
> >                                  'desc' : 'No such instance' },
> >               }
> > 
> >  Maybe we can verify what CIMOM is there on the machine and check the 
> > error information accordingly  to fix this issue,
> >  but I remember that somebody says it isn't a good idea to check the 
> > cimom type in tc, any better idea?
> > 
> >  Thanks!
> 
> This isn't a difference in CIMOMs.  If you run with recent providers 
> with both sfcb and pegasus, the test will fail on systems.
> 
> This failure is due to a change in the providers - it's due to changeset 

> 721.  So you'll need to branch this test case so that the error messages 

> are appropriate for the given provider revision.

  Thanks - Kaitlin.
  I'll cook up a patch for this.

> 
> -- 
> Kaitlin Rupert
> IBM Linux Technology Center
> kaitlin at linux.vnet.ibm.com
> 
> _______________________________________________
> Libvirt-cim mailing list
> Libvirt-cim at redhat.com
> https://www.redhat.com/mailman/listinfo/libvirt-cim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/libvirt-cim/attachments/20081114/86b57f5e/attachment.htm>