Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #2095] Can't save cronk in 1.6-dev #579

Closed
icinga-migration opened this issue Nov 21, 2011 · 8 comments
Closed

[dev.icinga.com #2095] Can't save cronk in 1.6-dev #579

icinga-migration opened this issue Nov 21, 2011 · 8 comments
Milestone

Comments

@icinga-migration
Copy link

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

Created by tredel on 2011-11-21 07:48:19 +00:00

Assignee: mhein
Status: Resolved (closed on 2011-11-22 13:46:49 +00:00)
Target Version: 1.6
Last Update: 2012-03-26 11:20:50 +00:00 (in Redmine)


In 1.6-dev it's not possible to save a cronk.
Tested with revision f1a17ef.

Attachments

  • cronk.JPG Frankstar - 2012-03-26 09:54:43 +00:00

Changesets

2011-11-22 13:14:53 +00:00 by mhein 819ab0f

* Fixed cronk data model (fixes #2095)
@icinga-migration
Copy link
Author

Updated by mhein on 2011-11-21 07:53:53 +00:00

  • Assigned to set to mhein

@icinga-migration
Copy link
Author

Updated by mhein on 2011-11-22 10:49:57 +00:00

  • Status changed from New to Assigned

@icinga-migration
Copy link
Author

Updated by mhein on 2011-11-22 13:46:49 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset 819ab0f.

@icinga-migration
Copy link
Author

Updated by Frankstar on 2012-03-26 09:54:43 +00:00

  • File added cronk.JPG

    [root@srvnms01 icinga-web]# git log -1
    commit 2d78f1b
    Author: Jannis Mosshammer
    Date: Fri Mar 23 10:54:05 2012 +0100

      * Fixed missing component destruction when reloading whole cronks (fixes #24
    

Failure is back.
Cant save any cronk (custom cronk or standart cronk)

@icinga-migration
Copy link
Author

Updated by Frankstar on 2012-03-26 09:54:55 +00:00

  • Done % changed from 100 to 0

@icinga-migration
Copy link
Author

Updated by mhein on 2012-03-26 11:04:41 +00:00

  • Done % changed from 0 to 100

This depends on #2456. You'll have to make a database upgrade and assign the right "icinga.cronk.custom" to group icinga_user (or wherever you want).

1.6.2 and >= 1.7 you'll have to assign the right explicit.

Hope this helps. I created a 1.7 changelog file to indicate that issue.

Kind regards,
Marius.

@icinga-migration
Copy link
Author

Updated by Frankstar on 2012-03-26 11:16:54 +00:00

Thanks. Works fine.

@icinga-migration
Copy link
Author

Updated by Frankstar on 2012-03-26 11:20:50 +00:00

whats about

https://dev.icinga.org/issues/2096

this would help in this case.

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

No branches or pull requests

1 participant