Skip to content
This repository has been archived by the owner on Dec 13, 2022. It is now read-only.

Downtime of a renamed or disabled object can not be deleted/cancelled #3763

Closed
Iralein opened this issue Aug 13, 2015 · 2 comments
Closed

Downtime of a renamed or disabled object can not be deleted/cancelled #3763

Iralein opened this issue Aug 13, 2015 · 2 comments

Comments

@Iralein
Copy link

Iralein commented Aug 13, 2015

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

@Iralein 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 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 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
@julienmathis julienmathis added this to the Centreon 2.6.3 milestone Aug 31, 2015
@julienmathis julienmathis modified the milestones: Centreon-2.7, Centreon 2.6.3 Sep 10, 2015
@julienmathis
Copy link
Contributor

This problem is due to Centreon Broker. We are currently working on this issue ans hope providing a fix very soon

@Iralein
Copy link
Author

Iralein commented Dec 7, 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.

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

3 participants