NAV 5.5.2
An upgrade of a router generated several "Device SomeModule at router.domain had a software upgrade" (as expected), but also several
Subject: deviceNotice/None on router.domain from NAV, but no message template is defined.
Variable dump: {'_messages': None, 'alert_type': None, 'device': <Device: VB13030631>, 'event': <EventQueue: id=101132957, event_type_id='deviceNotice', source_id='ipdevpoll', target_id='eventEngine', netbox=<Netbox: router.domain> , subid='', state='x', time=datetime.datetime(2022, 12, 13, 13, 50, 53, 897695)>, 'event_type': <EventType: deviceNotice>, 'history_vars': {}, 'language': 'en', 'msgtype': 'email', 'netbox': <Netbox: router.domain>, 'severity': 3, 'source': <Subsystem: ipdevpoll>, 'state': 'x', 'subid': '', 'time': datetime.datetime(2022, 12, 13, 13, 50, 53, 897695), 'value': 100}
--Ingeborg
On Tue, 13 Dec 2022 14:27:57 +0100 Ingeborg Hellemo ingeborg.hellemo@uit.no wrote:
NAV 5.5.2
An upgrade of a router generated several "Device SomeModule at router.domain had a software upgrade" (as expected), but also several
Subject: deviceNotice/None on router.domain from NAV, but no message template is defined.
Yes, I've received several other similar reports. It appears ipdevpoll sometimes dispatches deviceNotice events withouth specifying which type of alert it should translate to - and there is no default alert message template defined for generic deviceNotice alerts.
I've posted this as a new issue here:
https://github.com/Uninett/nav/issues/2533
NAV 5.5.2
An upgrade of a router generated several "Device SomeModule at router.domain had a software upgrade" (as expected), but also several
Subject: deviceNotice/None on router.domain from NAV, but no message template is defined.
morten.brekkevold@sikt.no said:
An upgrade of a router generated several "Device SomeModule at router.domain had a software upgrade" (as expected), but also several > Subject: deviceNotice/None on router.domain from NAV, but no message template is defined.
Yes, I've received several other similar reports. It appears ipdevpoll sometimes dispatches deviceNotice events withouth specifying which type of alert it should translate to - and there is no default alert message template defined for generic deviceNotice alerts.
I've posted this as a new issue here:
We have now upgraded to NAV 5.6, but still receive the occational
Subject: deviceNotice/None on router.domain from NAV, but no message template is defined.
Variable dump: {'_messages': None, 'alert_type': None, 'device': <Device: n/a>, 'event': <EventQueue: id=102366114, event_type_id='deviceNotice', source_id='ipdevpoll', target_id='eventEngine', netbox=<Netbox: router.domain> , subid='', state='x', time=datetime.datetime(2023, 2, 21, 8, 46, 34, 685581)>, 'event_type': <EventType: deviceNotice>, 'history_vars': {}, 'language': 'en', 'msgtype': 'email', 'netbox': <Netbox: router.domain>, 'old_version': '86', 'severity': 3, 'source': <Subsystem: ipdevpoll>, 'state': 'x', 'subid': '', 'time': datetime.datetime(2023, 2, 21, 8, 46, 34, 685581), 'value': 100}
--Ingeborg
On Tue, 21 Feb 2023 09:17:30 +0100 Ingeborg Hellemo ingeborg.hellemo@uit.no wrote:
We have now upgraded to NAV 5.6, but still receive the occational
Subject: deviceNotice/None on router.domain from NAV, but no message template is defined.
Are you sure you are *actually* running ipdevpoll from NAV 5.6, or don't have multiple NAV installations running? The only code path in NAV 5.6 that posts deviceNotice events from ipdevpoll will always set a `new_version` attribute as well (using `N/A` if the value is missing), but this seems to be missing entirely from the dump you posted.
morten.brekkevold@sikt.no said:
Are you sure you are *actually* running ipdevpoll from NAV 5.6, or don't have multiple NAV installations running? The only code path in NAV 5.6 that posts deviceNotice events from ipdevpoll will always set a `new_version` attribute as well (using `N/A` if the value is missing), but this seems to be missing entirely from the dump you posted.
I shall make sure to restart everything. Hopefully you won't hear more about this issue from me...
--Ingeborg
On Tue, 21 Feb 2023 09:17:30 +0100 Ingeborg Hellemo ingeborg.hellemo@uit.no wrote:
We have now upgraded to NAV 5.6, but still receive the occational
Subject: deviceNotice/None on router.domain from NAV, but no message template is defined.
Are you sure you are *actually* running ipdevpoll from NAV 5.6, or don't have multiple NAV installations running? The only code path in NAV 5.6 that posts deviceNotice events from ipdevpoll will always set a `new_version` attribute as well (using `N/A` if the value is missing), but this seems to be missing entirely from the dump you posted.
Now I am sure I'm running NAV 5.6
First we receive one message:
Device FANTRAY 1 at router.domain had a hardware upgrade from 86 to version n/a.
Later we receive
Variable dump: {'_messages': None, 'alert_type': None, 'device': <Device: n/a>, 'event': <EventQueue: id=102529692, event_type_id='deviceNotice', source_id='ipdevpoll', target_id='eventEngine', netbox=<Netbox: router.domain> , subid='', state='x', time=datetime.datetime(2023, 3, 3, 8, 36, 43, 77434)>, 'event_type': <EventType: deviceNotice>, 'history_vars': {}, 'language': 'en', 'msgtype': 'email', 'netbox': <Netbox: router.domain>, 'new_version': 'n/a', 'old_version': '86', 'severity': 3, 'source': <Subsystem: ipdevpoll>, 'state': 'x', 'subid': '', 'time': datetime.datetime(2023, 3, 3, 8, 36, 43, 77434), 'value': 100}
Both messages are about the same netbox
--Ingeborg
On Fri, 03 Mar 2023 09:58:51 +0100 Ingeborg Hellemo ingeborg.hellemo@uit.no wrote:
Now I am sure I'm running NAV 5.6
[...]
Later we receive
Variable dump: {'_messages': None, 'alert_type': None,
[...]
'new_version': 'n/a', 'old_version': '86',
Pretty strange. We can now confirm that you seem to be running 5.6, since both `new_version` and `old_version` are present. But it's hard for us to imagine why `alert_type` is None here, as there is only one code path that posts these events, and AFAIK it always sets this value.
I believe Johanna is investigating, so I expect she will follow up with her findings.
On Wed, 08 Mar 2023 14:41:28 +0100 Morten Brekkevold morten.brekkevold@sikt.no wrote:
But it's hard for us to imagine why `alert_type` is None here, as there is only one code path that posts these events, and AFAIK it always sets this value.
I believe Johanna is investigating, so I expect she will follow up with her findings.
No follow-up has been spotted, so here's a quick update from me: We found the problem last week, and it turned out to be a fundamental issue with lack of transactional SQL when events are posted: The event engine will sometimes end up fetching incomplete events from the queue, as not all the variables associated with the event have been committed to the database yet.
See https://github.com/Uninett/nav/pull/2594 for details. Bugfix release is expected later today.
-
Ingeborg Hellemo -
Morten Brekkevold