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

Service Sets aren't fully restored if one is accidentally deleted. #1065

Closed
dubidubiduuu opened this issue Aug 8, 2017 · 3 comments · Fixed by #2420
Closed

Service Sets aren't fully restored if one is accidentally deleted. #1065

dubidubiduuu opened this issue Aug 8, 2017 · 3 comments · Fixed by #2420
Milestone

Comments

@dubidubiduuu
Copy link

If I accidentally klick on the delete Button of a service set and try to "restore former object" only an empty service set is restored.

"Restore former object" should restore the complete director configuration.

Steps to Reproduce (for bugs)

Create a service set "test_service_set" and add one or more services to it
Deploy Config
delete service set "test_service_set"
Go to Acitivity log and click on "Restore former object"

The service set is recreated empty.

Your Environment

  • Director version (System - About): 1.3.1
  • Icinga Web 2 version and modules (System - About): 2.4.1
  • Icinga 2 version (icinga2 --version): v2.6.3
  • Operating System and version: Red Hat Enterprise Linux Server 7.3
  • Webserver, PHP versions: httpd-2.4.6-45.el7 php-5.4.16-42
@Thomas-Gelf Thomas-Gelf added this to the 1.6.0 milestone Sep 5, 2018
@Thomas-Gelf
Copy link
Contributor

Thomas-Gelf commented Oct 30, 2018

There will be the new Configuration Basket in v1.6, which will make this possible. Moving this to v1.7, it's too late for 1.6

@Thomas-Gelf Thomas-Gelf modified the milestones: 1.6.0, 1.7.0 Oct 30, 2018
@Thomas-Gelf
Copy link
Contributor

This should have been fixed, with and without baskets. In case you're still facing problems with the current master please let me know.

@afeefghannam89
Copy link
Member

This Problem still existing in the actual master ref/NC/#732413

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

Successfully merging a pull request may close this issue.

3 participants