Skip to:

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

Exception in Vacuumd because of location monitor changes

Description

On a recent compilation of 17-SNAPSHOT, I found the following exception:

vacuumd.log

Indeed, the column in question doesn't exist on location_specific_status_changes

location_specific_status_changes

Here is the rule:

vacuumd-configuration.xml

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Seth Leger August 3, 2015 at 1:37 PM

Fixed by updating the column name.

commit 2c4bafd2580e5ca11745128648df3118b2409e5e

Seth Leger July 31, 2015 at 1:44 PM

I think locationmonitorid just needs to change to the new systemid column.

Fixed

Details

Assignee

Reporter

Components

Sprint

Fix versions

Affects versions

Priority

Parent

PagerDuty

Created July 31, 2015 at 10:23 AM
Updated August 3, 2015 at 5:36 PM
Resolved August 3, 2015 at 1:37 PM