Skip to content

Searching for a contact results in "Contact has no field named 'group'" error #19376

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.

Sign up for GitHub

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

Jump to bottom
Closed
duckw opened this issue May 2, 2025 · 0 comments · Fixed by #19389
Closed

Searching for a contact results in "Contact has no field named 'group'" error #19376

duckw opened this issue May 2, 2025 · 0 comments · Fixed by #19389
Assignees
@jeremystretch
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Milestone
v4.3.1

Comments

@duckw
Copy link

duckw commented May 2, 2025

Deployment Type

Self-hosted

NetBox Version

v4.3.0

Python Version

3.12

Steps to Reproduce

In the top search bar, perform a search that would match an existing contact.

Expected Behavior

No error.

Observed Behavior

Error page with:

<class 'django.core.exceptions.FieldDoesNotExist'>

Contact has no field named 'group'

Python version: 3.12.3
NetBox version: 4.3.0-Docker-3.3.0
@duckw duckw added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels May 2, 2025
@bctiemann bctiemann added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels May 2, 2025
@KPTheProf KPTheProf mentioned this issue May 2, 2025
Closed
@jeremystretch jeremystretch marked this as a duplicate of #19386 May 2, 2025
@jeremystretch jeremystretch self-assigned this May 2, 2025
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels May 2, 2025
jeremystretch added a commit that referenced this issue May 2, 2025
@jeremystretch
Fixes #19376: Fix FieldDoesNotExist exception when global search resu…
f51291d 
…lts include a contact
@jeremystretch jeremystretch mentioned this issue May 2, 2025
Merged
@jnovinger jnovinger added this to the v4.3.1 milestone May 2, 2025
@jeremystretch jeremystretch marked this as a duplicate of #19437 May 8, 2025
@jeremystretch jeremystretch pinned this issue May 8, 2025
@jeremystretch jeremystretch marked this as a duplicate of #19470 May 12, 2025
@jeremystretch jeremystretch unpinned this issue May 13, 2025
@jeremystretch jeremystretch mentioned this issue May 13, 2025
Merged
@dreng dreng mentioned this issue May 15, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jeremystretch jeremystretch

Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Milestone
v4.3.1
4 participants
@jnovinger @bctiemann @duckw @jeremystretch