first activation fails about ansible-collection-checkmk.general HOT 8 CLOSED

one more hint, the activation was done anyway. But then then the http-response 414 is not correct, but this might not a problem of the module.

from ansible-collection-checkmk.general.

I close this bug, because it is not a bug of the module.

from ansible-collection-checkmk.general.

I did not get a chance to reproduce this yet, so can you please share, why you do not think it is a bug anymore?

from ansible-collection-checkmk.general.

because of the API does the activation, it only gives the wrong feedback (414). So for me it seems the module is correct.

from ansible-collection-checkmk.general.

if you want i reopen the issue

from ansible-collection-checkmk.general.

I encountered this issue too, it seems to be caused by SSL. Wasn't able to test if it would work on trusted certificates, but I expect it's due to untrusted certs. Switching to HTTP (And disabling redirection to HTTPS if it was enabled) fixed it for me.

from ansible-collection-checkmk.general.

Actually upon looking more I don't think it's the same issue. Mine reported a HTTP code of "-1". I wish the error messages this module gives was more descriptive, "Error calling API" doesn't help anyone.

from ansible-collection-checkmk.general.

@ogaida keep it closed for now, I will look into it when I can and take appropriate action.
@diademiemi if the issue persists, please open a dedicated issue, so we can look into it.

from ansible-collection-checkmk.general.