Fixed
Details
Assignee
Benjamin ReedBenjamin ReedReporter
Jeff GehlbachJeff GehlbachLabels
Components
Sprint
NoneFix versions
Affects versions
Priority
Critical
Details
Details
Assignee
Benjamin Reed
Benjamin ReedReporter
Jeff Gehlbach
Jeff GehlbachLabels
Components
Sprint
None
Fix versions
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created October 24, 2017 at 10:15 PM
Updated October 31, 2017 at 1:42 PM
Resolved October 31, 2017 at 1:42 PM
Customer reported the following exception stack trace in eventd.log after upgrading from Meridian 2016 to Meridian 2017.1.1:
The culprit turned out to be a
duty-schedule
ingroups.xml
:Fixing it up as follows fixed the problem:
So it appears we need to trim the string before trying to parse its components. Maybe Castor did this for us?