-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 24.1.3, Meridian-2018.1.11
-
Fix Version/s: Meridian-2018.1.12, 25.0.0
-
Component/s: Web UI - Admin
-
Security Level: Default (Default Security Scheme)
-
Labels:None
-
Sprint:Horizon 2019 - August 21st, Horizon 2019 - August 28th, Horizon 2019 - September 4th
When adding or editing a scheduled outage, if a user wants to change the "Outage Type", an exception is thrown.
Initially, this section appears as a combo-box list with a button to set the type. Once chosen, if you want to change it, by clicking on the link about the type's name, you'll get the following exception (from jetty-server.log as the WebUI doesn't show any useful information about the exception):
2019-08-26 10:10:46,279 WARN [qtp1832367953-662127] o.e.j.s.HttpChannel: /opennms/admin/sched-outages/editoutage.jsp javax.servlet.ServletException: org.apache.jasper.JasperException: An exception occurred processing JSP page [/admin/sched-outages/editoutage.jsp] at line [318] 315: } 316: 317: if (request.getParameter("deleteOutageType") != null) { 318: theOutage.setType(null); 319: theOutage.clearTimes(); 320: } else { 321: if (request.getParameter("outageType") != null) { ... Caused by: java.lang.IllegalArgumentException: 'type' cannot be null! at org.opennms.netmgt.config.utils.ConfigUtils.assertNotNull(ConfigUtils.java:43) ~[opennms-config-model-24.1.3.jar:?] at org.opennms.netmgt.config.utils.ConfigUtils.assertNotEmpty(ConfigUtils.java:51) ~[opennms-config-model-24.1.3.jar:?] at org.opennms.netmgt.config.poller.outages.BasicSchedule.setType(BasicSchedule.java:88) ~[opennms-config-model-24.1.3.jar:?] at org.apache.jsp.admin.sched_002doutages.editoutage_jsp._jspService(editoutage_jsp.java:425) ~[?:?]
BTW, once this is fixed, I would expect to see a confirmation box, as the actual action should also eliminate the existing outages entries (as all of them rely on the chosen type).
