No logging when insufficient credentials for WAPI_USER

[blv-am3]

If the inflblox user used is set to read only, nothing indicates it. There is no logging att al in the webhook log, which makes an error that should be easy to find really hard to find.

[kuritka]

Hi @blv-am3,
thanks for pointing this out — I agree that without proper log indication it becomes harder to debug.

That said, the feedback is a bit broad. Could you please specify where you’d expect the missing log message (e.g., when the Infoblox API returns insufficient permissions, failed authentication, etc.)?

Alternatively, if you already have a concrete idea, feel free to open a PR — happy to review it quickly.

[blv-am3]

I can describe what happened.
I had a test user with too high credential in Infoblox and changed to a new username and password which was incorrectly configured by our DNS admin - only set to read only.

I restarted and got logs from the pod log, and checked also the webhook. Everyghing looked fine.
Then I tested to create a new dnsendpoint which should cause the webook to create a new CNAME.
Nothing happened. Nothing in the logs.

I don't know what error the webhook got from Infoblox, but probably 500-something i guess. Or some kind of deny from the API.
Given that I don't know what response Infoblox gives when denying to create a CNAME (or anything for that matter) it's a bit hard to tell when it should log. But if the webhook check the response and also report failures to create entries, it would be much easier to debug the installation.

[kuritka]

Hi @blv-am3 - by default there is LOG_LEVEL set to info. Did you try debug?

[blv-am3]

Yes. debug was the log level.

[blv-am3]

Anyways.. fail to create entries in Infoblox should be at least level WARNING... I'd say ERROR.