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.

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

VM device selection does not filter the list by the selected site #9728

Closed
abhi1693 opened this issue Jul 14, 2022 · 1 comment
Closed

VM device selection does not filter the list by the selected site #9728

abhi1693 opened this issue Jul 14, 2022 · 1 comment
Assignees
Labels
beta Concerns a bug/feature in a beta release status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@abhi1693
Copy link
Member

NetBox version

v3.3.0-beta1

Python version

3.9

Steps to Reproduce

  1. Create a new VM named vm1 and associate it to site DM-Akron and click Save
  2. Edit the same VM and click on the Device drop-down and choose the 1st entry from the list and click save

Expected Behavior

The device list should be pre-filtered by the already associated site

Observed Behavior

An error is thrown (this is good to have as validation but not so user-friendly approach)

image

@abhi1693 abhi1693 added the type: bug A confirmed report of unexpected behavior in the application label Jul 14, 2022
@jeremystretch jeremystretch added beta Concerns a bug/feature in a beta release status: accepted This issue has been accepted for implementation labels Jul 14, 2022
@jeremystretch jeremystretch self-assigned this Jul 15, 2022
@jeremystretch
Copy link
Member

Edit the same VM and click on the Device drop-down and choose the 1st entry from the list and click save

The issue is that the devices is list is not being filtered by the assigned site; easy enough to fix.

However, there's a second issue, where even if a device within that site is selected, an AttributeError exception is raised because a device has been selected but no cluster is assigned. This is because we're missing a validation rule for the cluster.

I'm going to resolve both bugs under this issue as they're very closely related.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
beta Concerns a bug/feature in a beta release status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants