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

Reverting back any rule set to its defaults, deletes all rule sets #470

Closed
distahl opened this issue Dec 20, 2022 · 1 comment
Closed

Reverting back any rule set to its defaults, deletes all rule sets #470

distahl opened this issue Dec 20, 2022 · 1 comment
Assignees
Labels
Milestone

Comments

@distahl
Copy link

distahl commented Dec 20, 2022

Expected Behavior

When reverting back a rule set to its default values, only this specific rule set should be deleted in database.

Current Behavior

If reverting back a rule set, e.g. for hosts, to its default values. All other rule sets (vms, datastore) are getting also deleted from database.

Possible Solution

Please only delete rule set affected. Not all.

Steps to Reproduce (for bugs)

  1. Change rule set for hosts by setting different uptime values and save.
  2. Change rule set for vms by setting different uptime values and save.
  3. Remove uptime values from rule set for vms again. This way it should be considered the default again. Now, if you click save, not only the rule set for vms gets deleted from database, but also the rule set for hosts

Your Environment

  • VMware vCenter®/ESXi™-Version: 6.7.0
  • Version/GIT-Hash of this module: 1.5.0
  • Icinga Web 2 version: 2.10.3
  • Operating System and version: Oracle Linux 8.7
  • Webserver, PHP versions:
    • Apache (httpd): 2.4.37-51.0.1.module+el8.7.0+20778+02173b8e
    • PHP : 7.4.30-1.module+el8.7.0+20800+8e29b882
@Thomas-Gelf Thomas-Gelf self-assigned this Jan 10, 2023
@Thomas-Gelf Thomas-Gelf added this to the v1.6.0 milestone Jan 10, 2023
@Thomas-Gelf
Copy link
Contributor

Can be reproduced, affects only the main node ("All vCenters"), will be fixed

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

No branches or pull requests

2 participants