mcc does not update maximum threshold value for interfaces
Bug #901623 reported by
Morten Brekkevold
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Network Administration Visualized |
Fix Released
|
High
|
Morten Brekkevold | ||
| 3.10 |
Fix Released
|
High
|
Morten Brekkevold | ||
| 3.9 |
Fix Released
|
High
|
Morten Brekkevold | ||
Bug Description
mcc.py is supposed to update the max value for thresholds on interfaces on every run, but a bug in its SQL statement causes it to never update existing rrd_datasource entries.
Specifically, the query updates the datasource row if the units or max columns have different values than the new ones, using the "<>" operator. Unfortunately, this doesn't work when the columns have NULL values.
| Changed in nav: | |
| status: | Confirmed → In Progress |
Revision history for this message
| Morten Brekkevold (mbrekkevold) wrote | #1 |
| Changed in nav: | |
| milestone: | 3.9.4 → none |
Revision history for this message
| Morten Brekkevold (mbrekkevold) wrote | #2 |
Revision history for this message
| Morten Brekkevold (mbrekkevold) wrote | #3 |
| Changed in nav: | |
| status: | In Progress → Fix Committed |
| Changed in nav: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
The bug is also present in the completely refactored mcc code in trunk