Yikes! I haven't seen this... I made a ticket to test it out.
http://dev.zenoss.org/trac/ticket/896
-EAD
On Jan 18, 2007, at 9:21 PM, David Carmean wrote:
Seems to be related to me moving stuff around in the /Devices
tree. I've
now caused it to throw exceptions for keys without spaces (e.g.
'172.17' is
the latest).
On Thu, Jan 18, 2007 at 07:53:46AM -0800, David Carmean wrote:
Here's what I find about that exception:
exception KeyError
Raised when a mapping (dictionary) key is not found in the set
of existing keys.
So something is causing it to look for old keys, and you may or may
not want to handle this exception depending on whether it's my
screwup or a bug :)
On Wed, Jan 17, 2007 at 11:40:02PM -0500, Erik A. Dahl wrote:
Hum think spaces shouldn't be an issue... added at ticket to
check it
out.
http://dev.zenoss.org/trac/ticket/881
-EAD
On Jan 17, 2007, at 10:55 PM, David Carmean wrote:
Did we somehow enrage the Python Gods by using spaces in our /
Device tree
pathnames? I've actually gone and got rid of all the component
names
with spaces in them but this error persists:
--
David Carmean Network Appliance, Inc
Infosystems Architect, 495 E. Java Drive
Java (Sunnyvale) Engineering Lab Services Sunnyvale, CA 94089
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
--
David Carmean Network Appliance, Inc
Infosystems Architect, 495 E. Java Drive
Java (Sunnyvale) Engineering Lab Services Sunnyvale, CA 94089
_______________________________________________
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
