[dev.icinga.com #2179] Instances cronk display empty - error "Couldn't find class oc" #617

Closed
icinga-migration opened this Issue Dec 12, 2011 · 4 comments

Projects

None yet

1 participant

@icinga-migration
Member

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

Created by ralfk on 2011-12-12 13:35:24 +00:00

Assignee: jmosshammer
Status: Resolved (closed on 2012-02-20 18:30:24 +00:00)
Target Version: 1.6.2
Last Update: 2012-05-30 14:34:09 +00:00 (in Redmine)


The Instances cronk does not show anything. I get the following error in debug file:

[Mon Dec 12 14:29:00 2011] [error] Fetch failed with message Couldn't find class oc
 Query: (No query created) 
TargetStore info (IcingaApiModel): 
                 - Store target: IcingaInstances
                 - Searchtype:

Important: I am pretty sure that this only happens under following conditions:

  • The web GUI user is not member of all host and service definitions (1) AND
  • "Only show items that contain a contact with this name in their contactgroup definitions" is enabled. (2)

If the user is member of all items the instance is displayed. If the definitions option (2) is disabled then it's also okay.

Maybe related to Bug #2178 which also occurs only under those conditions.


My system:
Icinga 1.6.1, Icinga Web 1.6.0, Linux 64 bit, MySQL 5.1.53

No of hosts: 350
No of services: 2500
No of hostgroups: 46
No of servicegroups: 47

Changesets

2012-02-20 12:38:16 +00:00 by jmosshammer 53c5ff6

* Added contact definitions to instances (fixes #2179)
@icinga-migration
Member

Updated by mhein on 2012-01-20 11:31:52 +00:00

  • Assigned to set to jmosshammer
  • Target Version set to 1.7
@icinga-migration
Member

Updated by mhein on 2012-02-10 09:23:14 +00:00

  • Target Version changed from 1.7 to 1.6.2
@icinga-migration
Member

Updated by jmosshammer on 2012-02-20 18:30:24 +00:00

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

Applied in changeset 53c5ff6.

@icinga-migration
Member

Updated by ralfk on 2012-05-30 14:34:09 +00:00

I can confirm that this bug is solved after I updated to 1.7.0.

@icinga-migration icinga-migration added this to the 1.6.2 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment