You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2022. It is now read-only.
If you rename or disable Services, which are in a downtime, you are not able to delete or cancel the downtime via GUI after monitoring restart. The services are actually not in downtime, which is correct, but you can see the old downtimes in the downtimelist.
Centreon 2.6.1 and CBD 2.8.2-5
To reproduce:
Set a downtime for two objects. Rename one object, disable the other. Restart Engine.
Result: The renamed service is not in a downtime anymore. Both downtimes are still listed in Services->Downtimes and can not be deleted or cancelled.
Regards,
Ira
The text was updated successfully, but these errors were encountered:
Iralein
changed the title
Multiple Downtimes of an object can not be deleted/cancelled
Downtime of a renamed object can not be deleted/cancelled
Aug 17, 2015
Iralein
changed the title
Downtime of a renamed object can not be deleted/cancelled
Downtime of a renamed or deleted object can not be deleted/cancelled
Aug 17, 2015
Iralein
changed the title
Downtime of a renamed or deleted object can not be deleted/cancelled
Downtime of a renamed or disabled object can not be deleted/cancelled
Aug 17, 2015
I've installed Centreon 2.6.6 and the issue is still present. The names (hostname or service_description) is now correct, if you've renamed it and restarted, but you still can't cancel the downtime.
More problematic right now is the fact, that the GUI presents the downtime-icon, but the system isn't in downtime because of the renaming.
Hello,
If you rename or disable Services, which are in a downtime, you are not able to delete or cancel the downtime via GUI after monitoring restart. The services are actually not in downtime, which is correct, but you can see the old downtimes in the downtimelist.
Centreon 2.6.1 and CBD 2.8.2-5
To reproduce:
Set a downtime for two objects. Rename one object, disable the other. Restart Engine.
Result: The renamed service is not in a downtime anymore. Both downtimes are still listed in Services->Downtimes and can not be deleted or cancelled.
Regards,
Ira
The text was updated successfully, but these errors were encountered: