Comment 2 for bug 1403365
Revision history for this message
| Morten Brekkevold (mbrekkevold) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
This has been re-reported by another customer, along with sufficient information to reproduce.
It appears there has been a subtle change between NAV version in how maintenance events are generated, which affects the ability to match old maintenance states with new offMaintenance alerts.
Older events seem to have been posted with the event subid attribute set to a NULL value, while new events are posted with the subid attribute set to an empty string. A computer will not consider these two things to be equal, causing the offMaintenance alert to go unmatched.
The result is that the existing maintenance state is not closed, but the event itself is forwarded as an alert to anyone who subscribes to it.