We are using 2.0.6.
We have created event class mappings which work fine in our
corporate environment.
We have added these mappings to a zenpack and imported the zenpack
into our staging environment. The mappings are visible through the
gui.
when traps arrive in the staging environment they are classified as
unknown even though the mapping they should match exists.
If we delete the mapping and create it afresh (exactly as it was
after importing via the zenpack) then the traps are correctly mapped.
We have tried restarting zenoss after the zenpacks and restarting
after remodelling to no avail.
The initial mappings were added to a zenpack by adding their parent
so we tried adding each individual mapping to the zenpack but it
still doesn't map alarms after loading the zenpack to the new zenoss
instance.
I'm unable to reproduce this problem on Zenoss 2.1. This sounds like a
potential unicode export/import related problem to do with the
eventClassKey. Here's how you can check if this is the case.
Run zendmd from the command line as the zenoss user, then find the
mapping like so: (this assumes the mapping is in the /Test event class
and is the only mapping in there)
dmd.Events.Test.instances()[0].eventClassKey
This should return the eventClassKey for your mapping in single
quotes. If it is prepended by the letter u, it was imported as unicode
and is likely the cause of your problem. Please let us know what you
find out.
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
