can't add a new connect between Software <> Version / Device <> Software <> Version

[frankie64]

In the formulars the selectboxes are empty.

• Software creations works.
• new Version: In formular I can't select the new software, box is empty (and with some manuell inputs no results in the data-list)
• new Installation: in formuar I cant select software and version

Versions:

NetBox release NetBox Community-ml&s v4.3.5 (2025-07-29)
Python version 3.11.2
Django version 5.2.4
PostgreSQL version PostgreSQL 15.12

Software Lifecycle Management: 1.8.2

[frankie64]

Update netbox 4.4.2: the same behavior

[wkoot]

We test against netboxcommunity/netbox:v4.2.3, do you have the problem there? And is there a stacktrace in your instance?

[frankie64]

I have the problems since 4.2.3 until the actual version. I see no stacktrace in browser. If I open the selectbox, the waiting cursor is showing, return to normal and the Box is empty. wkoot ***@***.***> schrieb am Mo., 6. Okt. 2025, 15:53:

…

*wkoot* left a comment (ICTU/netbox_slm#75) <#75 (comment)> We test against netboxcommunity/netbox:v4.2.3, do you have the problem there? And is there a stacktrace in your instance? — Reply to this email directly, view it on GitHub <#75 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGZWYVXKNESTU4VCCT4GATL3WJX5NAVCNFSM6AAAAACIMJIVBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNZRG44DONBUGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[frankie64]

Sorry, I answered your question not correct. I did not have this problem in version 4.2.3.

[MartVisser]

@frankie64 can you check the logs of the NetBox instance itself to look for a stacktrace? Or enable debug mode, so you can see the stacktrace in your browser.

[frankie64]

I enable debug and found in syslog this

2025-10-07T16:21:53.646991+02:00 netbox-test NetBox: django.request ERROR: Internal Server Error: /api/plugins/slm/softwareproducts/
Traceback (most recent call last):

  File "/opt/netbox/netbox/netbox/middleware.py", line 128, in __call__
    username = request.META[self.header]
               ~~~~~~~~~~~~^^^^^^^^^^^^^
KeyError: 'HTTP_REMOTE_USER'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/netbox-4.4.2/venv/lib/python3.11/site-packages/django/core/handlers/exception.py", line 55, in inner
    response = get_response(request)
               ^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox-4.4.2/venv/lib/python3.11/site-packages/django/core/handlers/base.py", line 197, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox-4.4.2/venv/lib/python3.11/site-packages/django/views/decorators/csrf.py", line 65, in _view_wrapper
    return view_func(request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox-4.4.2/venv/lib/python3.11/site-packages/rest_framework/viewsets.py", line 125, in view
    return self.dispatch(request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/netbox/netbox/api/viewsets/__init__.py", line 142, in dispatch
    return super().dispatch(request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox-4.4.2/venv/lib/python3.11/site-packages/rest_framework/views.py", line 515, in dispatch
    response = self.handle_exception(exc)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox-4.4.2/venv/lib/python3.11/site-packages/rest_framework/views.py", line 475, in handle_exception
    self.raise_uncaught_exception(exc)
  File "/opt/netbox-4.4.2/venv/lib/python3.11/site-packages/rest_framework/views.py", line 486, in raise_uncaught_exception
    raise exc
  File "/opt/netbox-4.4.2/venv/lib/python3.11/site-packages/rest_framework/views.py", line 512, in dispatch
    response = handler(request, *args, **kwargs)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/netbox/netbox/api/viewsets/mixins.py", line 50, in list
    return super().list(request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox-4.4.2/venv/lib/python3.11/site-packages/rest_framework/mixins.py", line 40, in list
    page = self.paginate_queryset(queryset)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox-4.4.2/venv/lib/python3.11/site-packages/rest_framework/generics.py", line 175, in paginate_queryset
    return self.paginator.paginate_queryset(queryset, self.request, view=self)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/netbox/netbox/api/pagination.py", line 20, in paginate_queryset
    raise QuerySetNotOrdered(
netbox.api.exceptions.QuerySetNotOrdered: Paginating over an unordered queryset is unreliable. Ensure that a minimal ordering has been applied to the queryset for this API endpoint.

[wkoot]

Are all migrations applied? What database backend are you using? Did you install custom middleware or other plugins?
Is this NetBox instance running behind a proxy (or Django) that's doing something with that HTTP_REMOTE_USER header?

[frankie64]

other plugins:
[Netbox contract] 2.4.2
[Software Lifecycle Management] 1.8.2
[Topology views] 4.3.0
Database-backend: PostgreSQL 15.12 (Debian 15.12-0+deb12u2)
database runs on the same machine as netbox.

We don't use a proxy and netbox-middleware in environment.
We use netbox out of the box, no special configurations.

All traffic between differnet networks runs over a firewall.
We use authorization via ldap and its works.
Other netbox-stuff is working.

Whats wrong with HTTP_REMOTE_USER?

[wkoot]

I don't exactly understand why you're getting the QuerySetNotOrdered exception, nor why the traceback starts with the middleware error:

  File "/opt/netbox/netbox/netbox/middleware.py", line 128, in __call__
    username = request.META[self.header]
               ~~~~~~~~~~~~^^^^^^^^^^^^^
KeyError: 'HTTP_REMOTE_USER'

In order to populate the selection boxes, a call to the API is made to fetch all the options. This api call apparently fails.
The stack trace reports a not-ordered QuerySet, it's unclear how the error regarding a HTTP_REMOTE_USER header is related.

I wonder if your LDAP auth is injected through this HTTP_REMOTE_USER header, but simply not passed in the api call.
That would explain why you're not getting data, but it doesn't explain why it would end up spitting out a QuerySet error.

[frankie64]

but parts of your plugs works.
for example I get a list oft Software/Versions/Installations. maybe its works also with api ?

[frankie64]

Can I give you further information, or would you like to take a quick look at our test system?

[MartVisser]

@frankie64 I'm able to reproduce your issue in NetBox version 4.3.6 with plugin version 1.8.2. It looks like they changed the REST API paginator in NetBox in version 4.3.5, see https://github.com/netbox-community/netbox/issues/18900 .

Plugin Developer Note: The fix for bug https://github.com/netbox-community/netbox/issues/18900 now raises explicit exceptions when API endpoints attempt to paginate unordered querysets. Plugin maintainers should review their API viewsets to ensure proper queryset ordering is applied before pagination, either by using .order_by() on querysets or by setting ordering in model Meta classes. Previously silent pagination issues in plugin code will now raise QuerySetNotOrdered exceptions and may require updates to maintain compatibility.

I created https://github.com/ICTU/netbox_slm/issues/76 to make the plugin compatible with NetBox version 4.4.x. We will try to find some time in the coming weeks to look at it.

In the meantime, feel free to submit a PR.