Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

outage editor problems

Description

I just upgraded from 1.8.2 to 1.8.3. Although I hadn't looked at the outage editor in 1.8.2, it appears to be broke in 1.8.3. When I create a new scheduled outage and attempt to add a node (or interface), I get a partial listing of nodes (or interfaces) on a scrollable list. However it doesn't show all nodes (or interfaces) when I scroll to the bottom, and there's no paging mechanism to get more.

also, hitting either of the "add" buttons without first selecting a node or interface causes errors. For add node:

java.lang.NumberFormatException: For input string: ""
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:470)
at java.lang.Integer.parseInt(Integer.java:499)
at org.opennms.web.WebSecurityUtils.safeParseInt(WebSecurityUtils.java:126)

for add interface, the error doesn't show up until you save:

ValidationException: The following exception occured while validating field: _outageList of class: org.opennms.netmgt.config.poller.Outages: The following exception occured while validating field: _interfaceList of class: org.opennms.netmgt.config.poller.Outage: The following exception occured while validating field: _address of class: org.opennms.netmgt.config.poller.Interface: does not match the required regular expression: "([01]?[0-9][0-9]?|2[0-4][0-9]|25[0-5])(\.([01]?[0-9][0-9]?|2[0-4][0-9]|25[0-5])){3}|(match-any)";

  • location of error: XPATH: /outages
    The following exception occured while validating field: _interfaceList of class: org.opennms.netmgt.config.poller.Outage: The following exception occured while validating field: _address of class: org.opennms.netmgt.config.poller.Interface: does not match the required regular expression: "([01]?[0-9][0-9]?|2[0-4][0-9]|25[0-5])(\.([01]?[0-9][0-9]?|2[0-4][0-9]|25[0-5])){3}|(match-any)"
    at org.exolab.castor.xml.FieldValidator.validate(FieldValidator.java:277)
    at org.exolab.castor.xml.util.XMLClassDescriptorImpl.validate(XMLClassDescriptorImpl.java:1048)
    at org.exolab.castor.xml.Validator.validate(Validator.java:127)
    at org.exolab.castor.xml.Marshaller.validate(Marshaller.java:2527)
    at org.exolab.castor.xml.Marshaller.marshal(Marshaller.java:824)
    at org.exolab.castor.xml.Marshaller.marshal(Marshaller.java:730)
    at org.opennms.netmgt.config.PollOutagesConfigManager.saveCurrent(PollOutagesConfigManager.java:397)

Version: 1.8.3

Server Time: Fri Aug 13 13:33:39 PDT 2010
Client Time: Fri Aug 13 2010 13:33:39 GMT-0700 (PST)
Java Version: 1.6.0_20 Sun Microsystems Inc.
Java Virtual Machine: 16.3-b01 Sun Microsystems Inc.
Operating System: Linux 2.6.26-2-amd64 (amd64)
Servlet Container: jetty/6.1.24 (Servlet Spec 2.5)
User Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8

Environment

Operating System: All Platform: All

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Seth Leger May 3, 2011 at 4:49 PM

I just fixed a problem in NetworkElementFactory that was preventing users from adding IPv6 addresses to scheduled outages on this page.

After reading through the rest of the comments, I think that this page is satisfying everyone's demands. I'm going to mark this issue as fixed. If you have more specific problems with the page, please open a new issue. Thanks!

Seth Leger April 28, 2011 at 3:20 PM

I made the wording tweak that was suggested in the most recent comment.

commit dcb184cee0f51f159b6c9f108288615f09c3baff

Michael October 19, 2010 at 8:53 AM

regarding ip address search: I needed this only for nodes that have the nodelabel set to the ip address. If the removal of non-numeric characters is fixed the search for ip addresses as nodelabels should work, too.

Maybe it would help if the header of the form uses "Nodelabel" instead of "Node" above the dropdown-box, so it is clear that only nodelabels can be used here for searching.

Seth Leger (community account) September 22, 2010 at 7:08 PM

OK I figured out what is going on in comment 1: all of the strings that are being entered are being interpreted as integers after non-numeric values are stripped out of the string. For instance, "r4_3" is being interpreted as integer 43. I'll fix this behavior.

The other issue is that searching by IP address in the node search doesn't intentionally work. It searches the node labels only so that only works when the node label is set to the IP address. I'll look into this and see if I can get it to work somehow.

Seth Leger (community account) September 21, 2010 at 2:52 PM

I have reproduced the issue in comment 4; it is due to incorrect logic when handling form submission parameters. The default action (the way the page is written) is to erroneously delete the first node entry.

I will fix this particular issue by breaking the page up into multiple forms.

Fixed

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

PagerDuty

Created August 13, 2010 at 4:34 PM
Updated January 27, 2017 at 4:25 PM
Resolved May 3, 2011 at 4:49 PM

Flag notifications