Todd,
That's quite strange, if only because that error hasn't been seen
elsewhere. Could you try changing the line:
metatypes = Set([x.meta_type for x in brains])
To:
metatypes = Set( [ str(x.meta_type) for x in brains ] )
My guess is that there's a meta_type==None in there somewhere, which
shouldn't happen. This will flush it out. At the very list it'll fix
the problem.
--Ian
On Oct 9, 2007, at 10:07 AM, Todd Davis wrote:
I'm still fighting the devices in 2.0.92. Anyone have any idea how
to fix
this? When pulling up an individual device, I get:
* Module Products.PageTemplates.Expressions, line 185, in
__call__
* Module Products.PageTemplates.Expressions, line 180, in _eval
* Module Products.PageTemplates.Expressions, line 85, in render
* Module Products.ZenModel.Device, line 1539, in
getDeviceComponentEventSummary
* Module Products.ZenEvents.EventManagerBase, line 629, in
getDeviceComponentEventSummary
* Module sets, line 429, in __init__
* Module sets, line 374, in _update
TypeError: unhashable type
The line that is causing the problem (in EventMangerBase.py) is:
metatypes = Set([x.meta_type for x in brains])
meta_type is added in the migration script (version 2.1.0). I've
tried
re-running this step of zenmigrate and it succeeds (although I
don't know
how to verify it). Every device throws the same error -- making
Zenoss
barely usable right now.
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
