[OpenNMS/opennms] bc9699: NMS-19096: Refresh NodeScan scan stamp on each sch...
Marshall Massengill via opennms-cvs <[email protected]> Fri, 24 Jul 2026 09:13:12 -0700
| Newsgroups | gmane.network.opennms.cvs |
|---|---|
| Message-ID | <OpenNMS/opennms/push/refs/heads/mm/NMS-19096-smoke/[email protected]> |
Branch: refs/heads/mm/NMS-19096-smoke
Home: https://github.com/OpenNMS/opennms
Commit: bc96994fa50f76789e35c9cae96cd56cf4951e8b
https://github.com/OpenNMS/opennms/commit/bc96994fa50f76789e35c9cae96cd56cf4951e8b
Author: Marshall Massengill <[email protected]>
Date: 2026-07-24 (Fri, 24 Jul 2026)
Changed paths:
M opennms-provision/opennms-provisiond/src/main/java/org/opennms/netmgt/provision/service/NodeScan.java
A opennms-provision/opennms-provisiond/src/test/java/org/opennms/netmgt/provision/service/NodeScanTest.java
Log Message:
-----------
NMS-19096: Refresh NodeScan scan stamp on each scheduled run
A NodeScan scheduled with scheduleWithFixedDelay is reused for every
periodic run, but m_scanStamp was set once in the constructor and never
advanced. Obsolete-interface deletion compares each interface's
ipLastCapsdPoll against this stamp, so a long-lived scheduled scan kept
comparing against a stale stamp and could not reap non-primary interfaces
that had gone away; only a manual rescan, which builds a fresh NodeScan,
removed them. Advance the stamp in reset(), which already runs at the
start of every scan.
To unsubscribe from these emails, change your notification settings at https://github.com/OpenNMS/opennms/settings/notifications
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/wiki/index.php?page=MailingListFaq
opennms-cvs mailing list
To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-cvs