-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Cable bulk import unsupported for power feed terminations #18008
Comments
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. However, this is a similar bug to what is presented in #17954 and has a similar resolution as what is proposed in #17995. I volunteer on fixing this case if that resolution is accepted. |
This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically. |
This seems like a duplicate of #17954. Will close this accordingly if no objections. |
This is a similar issue, but I was asked to open a new one for this use case specifically. |
OK, I missed that context. |
Deployment Type
Self-hosted
Triage priority
N/A
NetBox Version
v4.1.6
Python Version
3.12
Steps to Reproduce
Cable Bulk Import
screendcim.powerfeed
side_a_device
andside_b_device
are required fields, but are not relevant for that termination type.Expected Behavior
Cables can be bulk imported with a
termination_type
ofdcim.powerfeed
and scoped by the associated power panel.Observed Behavior
Device is a required field, but not applicable for the
dcim.powerfeed
termination type. A power panel field is not available to scope the termination name.The text was updated successfully, but these errors were encountered: