Skip to content
This repository has been archived by the owner on Oct 6, 2023. It is now read-only.

Timeperiod not applied on centreon-engine restart #3

Closed
ganoze opened this issue Apr 30, 2015 · 2 comments
Closed

Timeperiod not applied on centreon-engine restart #3

ganoze opened this issue Apr 30, 2015 · 2 comments
Assignees
Labels
Milestone

Comments

@ganoze
Copy link
Contributor

ganoze commented Apr 30, 2015

Comment from Mathieu Cinquin:

I just realized several tests on the consideration of timeperiod with centreon-engine. I noticed that when changing/adding a timeperiod with include or exclude exception of services, it is not applied after a restart of centreon-engine. To be considered it is necessary to perform a forced check on the services concerned.

Example :

- creation of a new timeperiod (monday->friday | 17:15-18:00) with exclude timeperiod (Time Range exceptions xxxx/xx/xx - xxxx/xx/xx | 00:00 - 24:00)
- update the timeriod on the concerned service
- export and restart centreon-engine configuration
- verification of the next check => NOK The next check date is not correct
- Force check on the concerned service
- verification of the next check => OK

Hope to have been clear.

@ganoze
Copy link
Contributor Author

ganoze commented Apr 30, 2015

Timeperiods code was entirely rewritten for the 2.0 release. This bug will therefore be fixed.

@ganoze ganoze closed this as completed Apr 30, 2015
@ganoze ganoze reopened this Apr 30, 2015
@ganoze ganoze added this to the 2.0.0 milestone Apr 30, 2015
@ganoze ganoze self-assigned this Apr 30, 2015
@ganoze
Copy link
Contributor Author

ganoze commented Jun 5, 2015

Fixed in master.

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

No branches or pull requests

1 participant