Bug 2354063

Summary: Bump pynetbox to version 7.3.4 supporting netbox 4.x and py3.9
Product: [Fedora] Fedora EPEL Reporter: Mark Tinberg <mark.tinberg>
Component: python-pynetboxAssignee: Orphan Owner <extras-orphan>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: epel9CC: extras-orphan, igor.raits
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mark Tinberg 2025-03-21 14:10:34 UTC 
Description of problem:

pynetbox 7.2.x no longer works with Netbox 4.x servers due to changed behavior of the LOGIN_REQUIRED setting so that it applies to even the root of the /api/ URL path, the first thing that pynetbox does is make an unauthenticated request to /api/ to get the API-Version header to support conditional logic, which returns 200 OK on Netbox 3.x but 403 Auth Required on 4.x, even though it does successfully report the API-Version in either case.  pynetbox 7.3.4 has a fix where both 200 and 403 are considered successful for the purposes of gathering the version info and pynetbox 7.3.4 claims to still support py3.9 which is the system python of EL9

https://github.com/netbox-community/pynetbox/releases/tag/v7.3.4
https://github.com/netbox-community/pynetbox/pull/616

Looks like there is only 3-4 code changes between 7.2.0 and 7.3.4 most changes are related to how documentation is built

https://github.com/netbox-community/pynetbox/compare/v7.2.0...v7.3.4

I don't know what the process is to version bump an EPEL package, or if that is even permitted, but thought I'd raise the issue since I need to fix this on my systems, I can patch this locally for now but either I should make my own in-house build of 7.3.4 to override the epel version, or we can update epel itself and fix it for everyone.

What do you think is the best course of action and do you have any time to visit this issue?  Thanks.