Skip to content
This repository has been archived by the owner on Jan 7, 2020. It is now read-only.

Invalid date listed as beginning time of Uchiwa silence window #800

Open
zenmetsu opened this issue Sep 20, 2018 · 3 comments
Open

Invalid date listed as beginning time of Uchiwa silence window #800

zenmetsu opened this issue Sep 20, 2018 · 3 comments

Comments

@zenmetsu
Copy link

zenmetsu commented Sep 20, 2018

Expected Behavior

Expected that a silence event will be created with the specified start and end times.

Current Behavior

When a client is silenced, regardless of the specified time for the scheduled window, when going to the silenced tab, all entries show "invalid date"

Additionally, querying the API endpoint shows that the event is not being created with the correct start time. When the silence window is being created, I select a date next week as the start time, however once created the silence event appears to be active immediately.

Possible Solution

Bug #705 reported the same issue over a year ago. I'm running Uchiwa 1.2.0 and have replicated this problem. I restarted Uchiwa and saw no change; the items remain listed with "invalid date" for the start time.

Your Environment

  • Uchiwa version used: 1.2.0
  • Sensu version used: 1.4.3
  • Operating System and version (e.g. Ubuntu 14.04): debian stretch container
@zenmetsu
Copy link
Author

Updated to Uchiwa 1.3.1 and observed same behavior.

@zenmetsu
Copy link
Author

screenshot_2018-09-20 clients uchiwa 2
screenshot_2018-09-20 silenced uchiwa

@zenmetsu
Copy link
Author

Note in screenshot that silence entry should start on 24-Sept at 2100 and expire 1 hour later, however the actual entries are created with current time as start time and expiration 1 hour from now. This is actually correct as querying the API endpoint shows that the entry was created without a start time and with 3600 sec as expiration.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant