All work
- Discovery doesn't create/place node in correct requisition for rangeNMS-8537Resolved issue: NMS-8537Seth Leger
- LDAP authorization fails - group to role mapping does not workNMS-4725Resolved issue: NMS-4725Seth Leger
- Restricted users see whole node list, something has changed from 1.8NMS-4434Resolved issue: NMS-4434Benjamin Reed
3 of 3
Discovery doesn't create/place node in correct requisition for range
Fixed
Description
Environment
Ubuntu 16.04
Acceptance / Success Criteria
None
Lucidchart Diagrams
Details
Assignee
Seth LegerSeth LegerReporter
Dany LDany LLabels
Components
Fix versions
Affects versions
Priority
Blocker
Details
Details
Assignee
Seth Leger
Seth LegerReporter
Dany L
Dany LLabels
Components
Fix versions
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created May 25, 2016 at 4:42 AM
Updated September 12, 2016 at 4:48 PM
Resolved July 12, 2016 at 10:24 AM
Activity
Show:
Seth LegerJuly 12, 2016 at 10:24 AM
This was fixed by changing the way that the RangeChunker emits DiscoveryJob messages. They are now grouped by foreign source and location properly. Marking as fixed.
commit c6803da54fd99f68f9fe842778bc77b719b4c3df
Seth LegerJune 28, 2016 at 9:38 PM
I've verified that this is a regression caused by the Discovery rearchitecture in OpenNMS 18. The RangeChunker needs to use the foreign sources specified for each range when submitting jobs.
Hi,
I had installed an ubuntu 16.04 and opennms 18.0
I have a discovery like this
--------- <?xml version="1.0" encoding="UTF-8"?>
<discovery-configuration
xmlns="http://xmlns.opennms.org/xsd/config/discovery"
location="localhost" packets-per-second="1.0"
initial-sleep-time="30000" restart-sleep-time="86400000">
<include-range retries="1" timeout="2000" foreign-source="5219">
<begin>10.80.2.10</begin>
<end>10.80.2.254</end>
</include-range>
<include-range retries="1" timeout="2000" foreign-source="5219">
<begin>10.100.2.2</begin>
<end>10.100.2.2</end>
</include-range>
<include-range retries="1" timeout="2000" foreign-source="5200">
<begin>10.81.8.10</begin>
<end>10.81.8.20</end>
</include-range>
<include-range retries="1" timeout="2000" foreign-source="5200">
<begin>10.101.8.2</begin>
<end>10.101.8.2</end>
</include-range>
</discovery-configuration>
------------ when i restart discovery all node discovered are added to default requisition
If I test the same config file in version 17.1 (new install and same ubuntu version)
the discovery create the right requisition and put the node correctly
new behavior in 18 or Bug ?