Skip to content
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

Device search limited to non-racked devices when creating a new connection #3044

Closed
shugotek opened this issue Apr 4, 2019 · 3 comments
Closed

Device search limited to non-racked devices when creating a new connection #3044

shugotek opened this issue Apr 4, 2019 · 3 comments
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@shugotek
Copy link

shugotek commented Apr 4, 2019

Environment

  • Python version: 3.6.7
  • NetBox version: 2.5.9

Steps to Reproduce

1.Go on device
2.Select "Connect" on one interface
3.Search a device with "Search" function

Expected Behavior

List all device, and can filter if we write anything

Observed Behavior

List only non-racked device and finally "search" become unusable
@DanSheps
Copy link
Member

DanSheps commented Apr 4, 2019

Caused by rack_id=null not showing all racks.

@DanSheps DanSheps added status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application labels Apr 4, 2019
@DanSheps
Copy link
Member

DanSheps commented Apr 4, 2019

Looks like this was added in f6345b9 inadvertently

@candlerb
Copy link
Contributor

candlerb commented Apr 4, 2019

Darn, I just picked this up too :-) When searching for "wrn", tcpdump shows:

GET /api/dcim/devices/?q=wrn&brief=1&limit=50&offset=0&rack_id=null

... so it only matches unracked devices.

@jeremystretch jeremystretch changed the title Function Search to creating a connection list only non-racked device Device search limited to non-racked devices when creating a new connection Apr 4, 2019
@DanSheps DanSheps mentioned this issue Apr 8, 2019
Closed
@jeremystretch jeremystretch mentioned this issue Apr 8, 2019
Merged
@shugotek shugotek mentioned this issue Jul 17, 2019
Closed
@lock lock bot locked as resolved and limited conversation to collaborators Jan 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@candlerb @DanSheps @shugotek