-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
InfobloxConnectionError Hides reason for failed query #354
Comments
Hi @scetron, Thanks for bringing up this issue, we will take try and fix it in our next release. |
Hi @scetron, with the below script we tried to check the issue, the actual error is coming as a warning in to the console log.
As same error is being reproduced with the script but as a log it is also sharing the actual content of the response received from the NIOS API as below:. 2024-10-22 15:35:47,886 — infoblox_client.connector — WARNING — Failed on object search with url https://172.28.83.33/wapi/v2.10/ipv4address?network=10.100.12.0%2F24: b'{ "Error": "AdmConProtoError: 10.100.12.0/24 does not match any network",\n "code": "Client.Ibap.Proto",\n "text": "10.100.12.0/24 does not match any network"\n}'
|
The InfobloxConnectionError returned when searching for IPv4Address objects (that don't exist) hides the error response from Infoblox that the network does not exist and gives an invalid URL instead.
The error should be more descriptive at the very least. I would argue that the error is wrong as technically the URL is correct.
The text was updated successfully, but these errors were encountered: