Content Comparison

Since check 2.1, the DCD uses the REST API. Checkmk 1.6 is using the WEB-API to create a host (Checkmk REST API)

2022-05-13 13:37:35,970 [10] [cmk.dcd.web_api] > [GET] http://localhost:5005/mysite/check_mk/api/1.0/domain-types/host_config/collections/all 

2022-05-13 13:38:28,917 [10] [cmk.dcd.web_api] > [POST] http://localhost:5005/mysite/check_mk/api/1.0/domain-types/host_config/actions/bulk-create/invoke ((), {'data': None, 'json': {'ent
ries': [{'host_name': 'aws', 'folder': '/', 'attributes': {'locked_by': {'site_id': 'mysite', 'program_id': 'dcd', 'instance_id': 'connection_1'}, 'locked_attributes': ['cb', 'labels', 's
ite', 'tag_address_family', 'tag_agent'], 'site': 'mysite', 'labels': {'ds': 'pgb'}, 'tag_address_family': 'no-ip', 'tag_agent': 'no-agent', 'cb': 'hh'}}]}, 'params': {'bake_agent': 'fals
e'}})

2022-05-13 13:38:28,917 [10] [cmk.dcd.web_api] > [POST] http://localhost:5005/mysite/check_mk/api/1.0/domain-types/host_config/actions/bulk-create/invoke ((), {'data': None, 'json': {'ent
ries': [{'host_name': 'aws', 'folder': '/', 'attributes': {'locked_by': {'site_id': 'mysite', 'program_id': 'dcd', 'instance_id': 'connection_1'}, 'locked_attributes': ['cb', 'labels', 's
ite', 'tag_address_family', 'tag_agent'], 'site': 'mysite', 'labels': {'ds': 'pgb'}, 'tag_address_family': 'no-ip', 'tag_agent': 'no-agent', 'cb': 'hh'}}]}, 'params': {'bake_agent': 'fals
e'}})

ERROR An exception occurred
Traceback (most recent call last):
	File “/omd/sites/mysite/lib/python3/cmk/cee/dcd/connectors.py:, line 229, in _execute_phase2
		Cmk hosts = self._web_api.get_all_hosts()
	File “/omd/sites/mysite/lib/python3.9/site-packages/request/models.py:, line 960, in raise_for_status…
		Raise HTTPError (http_error_msg, response=self)
request.exceptions.HTTPError: 500 Server Error: INTERNAL SERVER ERROR for url:
http://localhost:5005/mysite/check_mk/api/1.0/domain-types/host_config/collections/all

In that case, custom attributes were used, which caused trouble. In this specific case, the wato plugin "wato_geo_fields.py" from the Checkmk treasures was used.

A workaround would be to remove all custom values and run the DCD again. This issue is already reported internally.