Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Downtimes set with 'All Services' don't propagate removal when removing the host downtime #4295

Closed
willfurnell opened this issue Dec 15, 2020 · 1 comment

Comments

@willfurnell
Copy link

Describe the bug

When setting a host downtime, I can check 'All Services' to have the downtime to apply to all the hosts services. However, when removing the host downtime, the module doesn't remove the downtimes it set on the services.

To Reproduce

  1. Have hostdowntime_all_services=1 set in the monitoring module configuration
  2. Create a new fixed downtime for a host
  3. Do some work on the host that takes less time than the fixed downtime period
  4. Click 'x' next to the host downtime to remove it
  5. Services are still in downtime until the end of the period

Expected behavior

If I check 'All Services' when making a downtime, I expect the downtime to be removed from them when I remove this downtime from the host.

Screenshots

Your Environment

Include as many relevant details about the environment you experienced the problem in

  • Icinga Web 2 version and modules (System - About):
    Icinga Web 2 Version
    2.8.2
    Git commit
    8a89839
    PHP Version
    7.3.11
    Git commit date
    2020-08-17

  • Web browser used: Firefox 83

  • Icinga 2 version used (icinga2 --version): 2.12.2-1

  • Server operating system and version: CentOS 7

Additional context

@nilmerg
Copy link
Member

nilmerg commented Jan 11, 2021

Duplicate of Icinga/icinga2#10333

@nilmerg nilmerg closed this as completed Jan 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants