Maintenance system stops working when an IP device on maintenance is deleted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Network Administration Visualized |
Fix Released
|
Critical
|
Morten Brekkevold |
Bug Description
Under NAV 4.2 (up to 4.2.1), if an IP device currently on endless ("until up") maintenance is deleted from NAV, the maintenance engine (maintengine) will crash on every run, effectively rendering the entire maintenance system broken. No new maintenance tasks will be activated, and active ones will remain active indefinitely.
The problem occurs because maintengine will attempt to extract information about the deleted component from the maintenance task. Traceback from maintengine.log looks like this:
[2014-12-03 11:35:02,057] [ERROR] [pid=13467 nav.maintengine] An unhandled exception occurred:
Traceback (most recent call last):
File "/usr/lib/
check_
File "/usr/lib/
check_
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
end_time = subject.
AttributeError: 'NoneType' object has no attribute 'last_downtime_
Changed in nav: | |
status: | Fix Committed → Fix Released |
fix here: https:/ /nav.uninett. no/hg/stable/ rev/542456d30c0 b