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

[dev.icinga.com #12911] Services can not be restored in history #483

Closed
icinga-migration opened this issue Oct 13, 2016 · 7 comments
Closed
Labels

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/12911

Created by mfrosch on 2016-10-13 09:23:11 +00:00

Assignee: (none)
Status: New
Target Version: 1.3.1
Last Update: 2016-11-30 08:38:19 +00:00 (in Redmine)


When I try to restore a service to its previous state via the history, I get the following error:

icinga_service has a multicolumn key, array required

This seems due to the service's object key consisting of host_id and name.

Here is a screenshot from the debugger:

multicolumn.png

multicolumn-gui.png

Attachments


Relations:

@icinga-migration
Copy link
Author

Updated by mfrosch on 2016-10-13 09:23:55 +00:00

  • Relates set to 11803

@icinga-migration
Copy link
Author

Updated by tgelf on 2016-10-24 05:46:24 +00:00

  • Target Version set to 1.2.0

@icinga-migration
Copy link
Author

Updated by tgelf on 2016-11-03 13:26:44 +00:00

  • Target Version changed from 1.2.0 to 1.3.0

@icinga-migration
Copy link
Author

Updated by tgelf on 2016-11-30 08:38:19 +00:00

  • Target Version changed from 1.3.0 to 1.3.1

@icinga-migration icinga-migration added this to the 1.3.1 milestone Jan 17, 2017
@Thomas-Gelf Thomas-Gelf removed this from the 1.3.1 milestone Feb 16, 2017
@aflatto
Copy link

aflatto commented Mar 20, 2018

I just encountered the same issue in the master from Jan 19
screenshot at 2018-03-20 12-22-43

@NeverUsedID
Copy link

NeverUsedID commented May 17, 2018

Same here with an "Apply Service For"-Rule.

If there are informations needed for debuging, please let me know

@Thomas-Gelf
Copy link
Contributor

This should have been fixed with v1.5.0 - in case there are still related issues please let us know.

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

4 participants