Admin app reports timezone mismatch when scheduling after DST

Steps to reproduce

If a capture agent is started before a daylight savings time switch over, and then the switch over occurs, the admin app will report a timezone mismatch with the agent.

I imagine it is likely something similar will happen if the admin server is started prior to DST and continues running after the change.

Restarting the agent solves this problem, but matterhorn should be smart enough to deal with this issue.

Status

Assignee

Greg Logan

Reporter

Jonathan Felder

Severity

Incorrectly Functioning With Workaround

Tags (folksonomy)

None

Components

Fix versions

Affects versions

1.4.0

Priority

Major
Configure