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

Error message hidden on VLAN Group tab when editing a VLAN with both Group and Site configured #11816

Closed
jhammond-git opened this issue Feb 23, 2023 · 8 comments · Fixed by #14609
Assignees
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

Comments

@jhammond-git
Copy link

jhammond-git commented Feb 23, 2023

NetBox version

v3.4.2

Python version

3.8

Steps to Reproduce

  1. Create site named Site1 with the automatically assigned slug and all other settings as default
  2. Create VLAN group named VLAN_Group with the automatically assigned slug and all other settings as default
  3. Create new vlan id 4000 named VLAN_4000. Add it to Site1, leaving all other settings default.
  4. Edit the new vlan. Add it to vlan group VLAN_Group and click Save.

Expected Behavior

Page should reload with an error stating what the problem is (this can be seen when trying to create a new vlan with both a site assignment and a vlan group assignment).

Observed Behavior

Page reloads with the error message hidden on the VLAN Group tab.

@jhammond-git jhammond-git added the type: bug A confirmed report of unexpected behavior in the application label Feb 23, 2023
@jeremystretch
Copy link
Member

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@jeremystretch jeremystretch added the status: revisions needed This issue requires additional information to be actionable label Feb 23, 2023
@jhammond-git
Copy link
Author

Sorry, I wasn't trying to be obtuse. I can add steps such as "create a site", "create a vlan group" if needed. Is that the level of detail you're looking for?

@jsenecal
Copy link
Contributor

@jhammond-git you must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing.

@jhammond-git
Copy link
Author

jhammond-git commented Feb 23, 2023

I understand. I obviously missed my mark and ended up way too far in the "brevity" end of the field. Are the edited instructions sufficient?

@kkthxbye-code
Copy link
Contributor

Page reloads with no indication of why the edit failed, or even that it failed, other than still being in the Edit form.

The error is in the VLAN Group "tab", you just have to switch to it:

image

I guess the issue is that the tab isn't switched to the VLAN Group "tab", but I'm not sure how to best handle that to be honest. The active tab is the one that is set, which is still the Site "tab". I guess we could throw a generic validation error (instead or in addition), which should show up as a toast instead.

Could you please update the issue to correct the observed behavior and give the issue a proper title instead of "No error message when". Thanks.

@jeremystretch
Copy link
Member

Quick tangent:

I guess the issue is that the tab isn't switched to the VLAN Group "tab", but I'm not sure how to best handle that to be honest.

Under the feature branch #11625 now gives us the ability to re-render forms based on a selected value. One option would be to change the tabs to a "type" selector and render only the fields relevant to the selected type. (I'm doing this already with the new DataSource model, which will include backend-specific configuration fields depending on the selected backend.) Probably worth a separate discussion.

@jhammond-git jhammond-git changed the title No error message when Error message hidden on VLAN Group tab when editing a VLAN with both Group and Site configured Feb 24, 2023
@jhammond-git
Copy link
Author

Let me know if the edits don't cover what you wanted. Not sure how I didn't finish the title the first time.

@kkthxbye-code kkthxbye-code added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation and removed status: revisions needed This issue requires additional information to be actionable labels Feb 24, 2023
@jeremystretch
Copy link
Member

Marking this as blocked by #11891.

@jeremystretch jeremystretch added status: blocked Another issue or external requirement is preventing implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Mar 13, 2023
@jeremystretch jeremystretch added the severity: low Does not significantly disrupt application functionality, or a workaround is available label Jun 23, 2023
@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation and removed status: blocked Another issue or external requirement is preventing implementation labels Dec 27, 2023
@jeremystretch jeremystretch self-assigned this Dec 27, 2023
@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 Dec 27, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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
Development

Successfully merging a pull request may close this issue.

4 participants