You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Getting ConnectionError which raises BadStatusLine error, even when IP is allocated:
http.client.BadStatusLine: {"id":384,"url":"http://192.168.122.209:8000/api/ipam/ip-addresses/384/","display":">[10.10.0.19/24](https://10.10.0.19/24)","family":{"value":4,"label":"IPv4"},"address":"[10.10.0.19/24](https://10.10.0.19/24)","vrf":{"id":1,"url":"http://192.168.122.209:8000/api/ipam/vrfs/1/","display":"admin","name":"admin","rd":null},"tenant":null,"status":{"value":"active","label":"Active"},"role":null,"assigned_object_type":null,"assigned_object_id":null,"assigned_object":null,"nat_inside":null,"nat_outside":[],"dns_name":"","description":"","tags":[],"custom_fields":{},"created":"2022-12-21T13:08:20.549255Z","last_updated":"2022-12-21T13:08:20.549284Z"}HTTP/1.1 201 Created
One more problem here is that the HTTP status goes after the response json.
The text was updated successfully, but these errors were encountered:
pynetbox does not raise ConnectionErrors, it's some underlying module that's doing that.
Are you using the same pynetbox.api object (= the same requests.Session) in all those threads? I'm not a Python threading expert but I'm thinking if that could cause the responses to get messed up. See also: psf/requests#2766
Trying to allocate IP in a few threads in parallel via :
Getting ConnectionError which raises BadStatusLine error, even when IP is allocated:
One more problem here is that the HTTP status goes after the response json.
The text was updated successfully, but these errors were encountered: