CMK version: 2.0.0p25
OS version: Ubuntu 20.04 LTS
Hallo zusammen,
Wir bekommen bei Abfrage aller Nutzer über die REST-API folgende Fehlermeldung:
"TypeError: argument of type ‘bool’ is not iterable"
Unsere Benutzer werden dabei aus unserem OpenLDAP Server synchronisiert.
Hier einmal die vollständige Fehlermeldung:
"title": "Internal Server Error",
"status": 500,
"detail": "argument of type 'bool' is not iterable",
"crash_id": "b35be59e-ead9-11ec-a073-e5868111a6f3",
"crash_report": {
"href": "http://hostname/cmk/check_mk/crash.py?crash_id=b35be59e-ead9-11ec-a073-e5868111a6f3&site=jsc",
"method": "get",
"rel": "cmk/crash-report",
"type": "text/html"
},
"stack_trace": [
"Traceback (most recent call last):",
" File \"/omd/sites/cmk/lib/python3/cmk/gui/wsgi/applications/rest_api.py\", line 403, in _wsgi_app",
" return wsgi_app(environ, start_response)",
" File \"/omd/sites/cmk/lib/python3/cmk/gui/wsgi/applications/rest_api.py\", line 207, in __call__",
" wsgi_app = self.func(ParameterDict(path_args))",
" File \"/omd/sites/cmk/lib/python3/cmk/gui/plugins/openapi/restful_objects/decorators.py\", line 618, in _wrapper",
" response = func(param)",
" File \"/omd/sites/cmk/lib/python3/cmk/gui/plugins/openapi/restful_objects/decorators.py\", line 548, in _validating_wrapper",
" response = self.func(param)",
" File \"/omd/sites/cmk/lib/python3/cmk/gui/plugins/openapi/endpoints/user_config.py\", line 62, in list_users",
" user_attributes = _internal_to_api_format(attrs)",
" File \"/omd/sites/cmk/lib/python3/cmk/gui/plugins/openapi/endpoints/user_config.py\", line 197, in _internal_to_api_format",
" api_attrs.update(_notification_options_to_api_format(internal_attrs))",
" File \"/omd/sites/cmk/lib/python3/cmk/gui/plugins/openapi/endpoints/user_config.py\", line 273, in _notification_options_to_api_format",
" if \"timerange\" in internal_notification_options:",
"TypeError: argument of type 'bool' is not iterable",
""
]
}
Es scheint also an den Einstellungen der Notifications zu liegen.
Habt ihr vielleicht eine Idee, woran das liegen könnte? Ist das ein Konfigurationsfehler von unserer Seite?