AlertEngine crash: global name 'TimePeriod' is not defined
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Network Administration Visualized |
Fix Released
|
High
|
Thomas Adamcik |
Bug Description
AlertEngine has been found to crash with this as its last log entry:
[2008-12-01 08:45:45,757] [CRITICAL] [pid=17439 nav.alertengine] Unhandeled error: global name 'TimePeriod' is not defined
Traceback (most recent call last):
File "/usr/lib/
check_
File "/usr/lib/
sent_daily, sent_weekly = handle_
File "/usr/lib/
valid_during = [TimePeriod.
NameError: global name 'TimePeriod' is not defined
Looks like missing import which hits us when someone queues for the next time periode in their profile.
Changed in nav: | |
assignee: | nobody → adamcik |
importance: | Undecided → High |
milestone: | none → v3.5.0b3 |
status: | New → Confirmed |
Changed in nav: | |
status: | Fix Committed → Fix Released |
http:// metanav. uninett. no/hg/default/ rev/5ef48c41861 7