Release 1.13

Release 1.13.4

Release 1.13.4 is the 5th unstable release; it is a preview of what will eventually become the OpenNMS 1.14.x stable series.

The codename for 1.13.4 is Metallica

Bug
Enhancements

Release 1.13.3

Release 1.13.3 is the 4th unstable release; it is a preview of what will eventually become the OpenNMS 1.14.x stable series. It contains a critical security fix.

The codename for 1.13.3 is De Musikalske Dvergene

Bug
  • Security: downloadReport allow download and view any file in filesystem (Issue NMS-6580)

Release 1.13.2

Release 1.13.2 is the 3rd unstable release; it is a preview of what will eventually become the OpenNMS 1.14.x stable series. It contains a large number of changes over 1.13.1, including collection updates, lots of refactoring, more topology UI enhancements, auto-acknowledge notification updates, Linkd updates, VMware graph enhancements, and many other small improvements.

The codename for 1.13.2 is Boston

Bug
  • Using the Sftp3gppXmlCollectionHandler affecting the XSLT pre processing. Both are not working together. (Issue NMS-6533)

  • ResourceDao.findTopLevelResources() is returning duplicated data because of storeByForeignSource (Issue NMS-6545)

  • Notifications are truncated at 4000 chars in database (Issue NMS-6562)

  • The SFTP Connection are not closed when an exception is thrown using 3GPP XML Collector (Issue NMS-6564)

Enhancements
  • Patch for auto-acknowledgement of threshold events (Issue NMS-1462)

  • Embed JMS provider inside OpenNMS (Issue NMS-2638)

  • Add ability to match event parms for auto-ack (Issue NMS-3090)

  • Alphabetize the polling packages on scheduled outages (Issue NMS-5243)

  • Sort notifications by severity (Issue NMS-6504)

  • snmp mib compiler should use twin column select for systemDefs (Issue NMS-6525)

  • Make visible the scheduled outages that are being executed. (Issue NMS-6558)

Release 1.13.1

Release 1.13.1 is the 2nd unstable release; it is a preview of what will eventually become the OpenNMS 1.14.x stable series. It contains a large number of changes over 1.13.0, including Java 8 support, many core cleanups, support for running Camel and ActiveMQ in the OpenNMS Karaf container, MANY ReST-related cleanups for XML and JSON output, plus tons of other fixes and features.

The codename for 1.13.1 is Seigmen

Bug
  • REST API - Access to list of all user with non admin rights (Issue NMS-5391)

  • Linkd package not working (Issue NMS-6215)

  • Linkd LLDP discovery is not able to get links when one end point does not support LLDP mib (Issue NMS-6233)

  • Create Link to Topology from Node Page (Issue NMS-6339)

  • Can’t create a node without path outage information in provisioning web interface (Issue NMS-6350)

  • mib2 storage usage graph does not work with RRDtool (Issue NMS-6356)

  • Validate the mename of a maskelement when editing an event through the Vaadin UI (Issue NMS-6378)

  • The ILR reports wrong data when there are several packages with different collection rates on collectd-configuration.xml for the same service (Issue NMS-6386)

  • Deadlock in location_monitors update via Hibernate (Issue NMS-6392)

  • Exception thrown while changing transaction to readOnly mode (Issue NMS-6399)

  • Security Information disclosed in Service detail screen (Issue NMS-6403)

  • Provisiond detectors sometimes fail to detect (Issue NMS-6412)

  • Topology Widgets are out of sync with contextual window (Issue NMS-6416)

  • IP Interface component bug on Node Page (Issue NMS-6420)

  • NRTG Is busted in master (Issue NMS-6422)

  • Auto Refresh Interval in Topology APP isn’t consistent (Issue NMS-6423)

  • Links from Topology Map to Geographical Map are no longer working (Issue NMS-6425)

  • WebUI shows 503 for log in (Issue NMS-6435)

  • The Valere devices with broken SNMP agents are hanging Provisiond. (Issue NMS-6484)

  • Creating a scheduled outage from the node’s page doesn’t work (Issue NMS-6490)

  • Several XSD files are not being generated anymore. (Issue NMS-6491)

Enhancements
  • SVG Map: Clean Up Java Classes (Issue NMS-5013)

  • Add a regex to test the banner returned by the TCP monitor (Issue NMS-3218)

  • Greater flexibility in threshold event parameters (Issue NMS-5468)

  • New event file for Konica Traps (Issue NMS-5699)

  • Remove the reset button on the login prompt. (Issue NMS-5738)

  • Datacollection Konica Printers (Issue NMS-5781)

  • New BackupExec event file (Issue NMS-5789)

  • New mib/event file for TrendMicro AV (Issue NMS-5829)

  • New events/datacollection for Liebert USV (Issue NMS-5882)

  • Use a suitable Algorithm to display Elements in SVG maps (Issue NMS-6104)

  • Add Discovery Strategy to Links (Issue NMS-6106)

  • persist protocol used for discoved links (Issue NMS-6245)

  • Add BGP datacollection support for Foundry BigIron 4000/8000/RX (Issue NMS-6308)

  • Upgrade JasperReport Engine to current stable release (Issue NMS-6366)

  • Search for event from the last hour isn’t possible without Event Text (Issue NMS-6370)

  • apache jakarta regexp project is discontinued. (Issue NMS-6427)

  • Create Provisiond detector for VMwareCim-HostSystem (Issue NMS-6434)

  • Monitor for JMX related framework Jolokia (Issue NMS-6328)

Release 1.13.0

Release 1.13.0 is the first unstable release; it is a preview of what will eventually become the OpenNMS 1.14.x stable series. It contains a number of enhancements, most notably GUI work in the topology UI, as well as some code cleanup and other updates that are too invasive to include in 1.12.

The codename for 1.13.0 is Hedningarna

Bug
  • Maven surefire doesn’t properly report some test failures (Issue NMS-1698)

  • remote poller logging (Issue NMS-2800)

  • Cannot build using IBM’s java - Groovy maven plugin error "No providers discovered" (Issue NMS-3476)

  • ./maven/bin/mvn dependency:go-offline not fetch all dependences (Issue NMS-4304)

  • Jetty 503 Service Unavailable after disabling PollerBackend (Issue NMS-4330)

  • JMX jrb filenames can contain spaces (Issue NMS-4612)

  • Can’t disable all log rotation in log4j.properties (Issue NMS-4689)

  • DatabaseReportListController is never used? (Issue NMS-5034)

  • NullPointerException in DefaultParameterConversionService with IE8 (Issue NMS-5134)

  • Default ONMS JMX graphs broken with storeByGroup enabled (Issue NMS-5279)

  • redirection on cancel configuration changes for a KSC report returns to main opennms index page. (Issue NMS-5443)

  • manager log messages are too vague or wrong level. (Issue NMS-5467)

  • SNMPV3 context not working in provisiond (Issue NMS-5556)

  • "No Data for this Entry" in Serial Interface Utilization Summary report (Issue NMS-5617)

  • Make possible to set the interface status on the requisition through REsT and WebUI (Issue NMS-5773)

  • Selecting topology group doesn’t filter alarm widget (Issue NMS-5787)

  • VMware integration not gathering statistics on VM host hardware collections such as vmware4Disk or vmware4Cpu (Issue NMS-5845)

  • LLDP Failure for non ifIndex references (Issue NMS-5904)

  • Topology Map showing non-existent links/missing valid links (Issue NMS-5906)

  • Prefab graph ignores properties for width and height (Issue NMS-5918)

  • Primary interface is not used for VMware CIM service polling and data collection (Issue NMS-5938)

  • Default to Provisiond handling newSuspects, disabling Capsd (Issue NMS-5943)

  • Alarm list and alarm details is not showing in the WebUI (Issue NMS-5947)

  • Duplicated parameter in notification.xml (Issue NMS-5948)

  • Exception when switching tabs in alarm and node browsers on map (Issue NMS-5968)

  • Sorting doesn’t work on alarm and node browsers (Issue NMS-5969)

  • Node availability report wrong calculation of percentage (Issue NMS-5990)

  • Add foreignSource parameter to newSuspect Event (Issue NMS-5991)

  • "Servlet with alias already registered" Exception occurs on starupt in osgi container (Issue NMS-5999)

  • Negative filter for services in alarm list shows null (Issue NMS-6005)

  • Loading Vaadin parts of the WebUI needs a lot of time (Issue NMS-6043)

  • Database connections leak until the system cannot obtain any more connections (Issue NMS-6051)

  • Master doesn’t start due to PollerBackend Exception (Issue NMS-6052)

  • The VMWare collector doesn’t work properly when storeByForeignSource is enabled (Issue NMS-6060)

  • Make the VMWare Provisioner more useful (Issue NMS-6070)

  • provision.pl is not handling properly the 302 and 303 HTTP Responses. (Issue NMS-6072)

  • The JAR where the GpDetector is defined doesn’t appear on the RPM or DEB files (Issue NMS-6074)

  • VmwareConfigBuilder creates too long aliases for vSphere 5.1 (Issue NMS-6082)

  • Syslog Northbounder is not translating the node labels (Issue NMS-6092)

  • Linkd throws Exception when CdpCacheIpv4Address is blank (Issue NMS-6101)

  • Linkd does not update properly datalinkinterface table (Issue NMS-6102)

  • Linkd does not manage duplicated ip addresses (Issue NMS-6103)

  • Can’t use SNMPv3 with NoAuth-NoPriv (Issue NMS-6108)

  • NRTG is not working if storeByForeignSource is enabled (Issue NMS-6119)

  • XSS vector in admin/error.jsp (Issue NMS-6147)

  • LdapMonitor can leak poller threads (Issue NMS-6148)

  • VMware metrics for network packet statistics missing for ESX host (Issue NMS-6166)

  • GeoMap boundaries (Issue NMS-6172)

  • Unresolved constraint in bundle org.opennms.features.vaadin-node-maps (Issue NMS-6176)

  • Unresolved constraint in bundle org.opennms.features.jmxconfiggenerator (Issue NMS-6178)

  • Unresolved constraint in bundle org.opennms.features.jmxconfiggenerator.webui (Issue NMS-6179)

  • GeoMap doughnut markers don’t reflect alarm status (Issue NMS-6214)

  • 503 Webapp Error (Issue NMS-6217)

  • Exception while using topology history feature (Issue NMS-6218)

  • SnmpInterfaceRrdMigrator breaks with "javax.xml.bind.UnmarshalException: inf" (Issue NMS-6302)

  • send-event.pl invalid in master (Issue NMS-6304)

Enhancements
  • Refactor Log Level of OpenNMS Messages (Issue NMS-1087)

  • distributed monitor disconnected timeout hardcoded (Issue NMS-2797)

  • change the log rotation to use the log4j-extras RollingFileAppender (Issue NMS-2949)

  • log4j enhancement to support compression (Issue NMS-4690)

  • eclipse maven integration (Issue NMS-4814)

  • Add IS-IS discovey to Linkd (Issue NMS-5582)

  • JRobinRrdStrategy class does not support RGBA color values (Issue NMS-5591)

  • Add OAuth support to microblog notification feature (Issue NMS-5691)

  • keep all log4j settings near their main definition. (Issue NMS-5729)

  • Bump maven-resources-plugin to 2.6 to avoid annoying message during build (Issue NMS-5805)

  • Widget Filtering based on visible vertices (Issue NMS-5869)

  • Topology Selection Behavior improvements (Issue NMS-5870)

  • Changing RRD graph size with URL parameter width and height (Issue NMS-5919)

  • Tool converting JRobin files to RRDtool file format (Issue NMS-5921)

  • Detection for VMware CIM service only if the communication is possible (Issue NMS-5941)

  • Add a configuration foreignSource element/attribute to a discovery range (Issue NMS-5992)

  • Add new sysOID to linkd (Issue NMS-6039)

  • Ability to disable rescanning of updated nodes during import (Issue NMS-6040)

  • SNMP support for Clavister security devices (Issue NMS-6107)

  • Split Linkd Link dicovery as per discovery Stategy (Issue NMS-6110)

  • add provisioning requisition column to outages list display (Issue NMS-6143)