Cable bulk import unsupported for power feed terminations #10475

Closed
opened 2025-12-29 21:31:58 +01:00 by adam · 8 comments
Owner

Originally created by @sleepinggenius2 on GitHub (Nov 13, 2024).

Deployment Type

Self-hosted

Triage priority

N/A

NetBox Version

v4.1.6

Python Version

3.12

Steps to Reproduce

  1. Navigate to the Cable Bulk Import screen
  2. Try to enter data for a termination of type dcim.powerfeed
  3. The fields side_a_device and side_b_device are required fields, but are not relevant for that termination type.

Expected Behavior

Cables can be bulk imported with a termination_type of dcim.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.

Originally created by @sleepinggenius2 on GitHub (Nov 13, 2024). ### Deployment Type Self-hosted ### Triage priority N/A ### NetBox Version v4.1.6 ### Python Version 3.12 ### Steps to Reproduce 1. Navigate to the `Cable Bulk Import` screen 2. Try to enter data for a termination of type `dcim.powerfeed` 3. The fields `side_a_device` and `side_b_device` are required fields, but are not relevant for that termination type. ### Expected Behavior Cables can be bulk imported with a `termination_type` of `dcim.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.
adam added the type: bugpending closurestatus: blockedstatus: revisions needed labels 2025-12-29 21:31:58 +01:00
adam closed this issue 2025-12-29 21:31:58 +01:00
Author
Owner

@jsenecal commented on GitHub (Nov 14, 2024):

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 https://github.com/netbox-community/netbox/pull/17995.

I volunteer on fixing this case if that resolution is accepted.

@jsenecal commented on GitHub (Nov 14, 2024): 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 https://github.com/netbox-community/netbox/pull/17995. I volunteer on fixing this case if that resolution is accepted.
Author
Owner

@github-actions[bot] commented on GitHub (Dec 11, 2024):

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.

@github-actions[bot] commented on GitHub (Dec 11, 2024): 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.
Author
Owner

@bctiemann commented on GitHub (Dec 12, 2024):

This seems like a duplicate of https://github.com/netbox-community/netbox/issues/17954. Will close this accordingly if no objections.

@bctiemann commented on GitHub (Dec 12, 2024): This seems like a duplicate of https://github.com/netbox-community/netbox/issues/17954. Will close this accordingly if no objections.
Author
Owner

@sleepinggenius2 commented on GitHub (Dec 12, 2024):

This is a similar issue, but I was asked to open a new one for this use case specifically.

@sleepinggenius2 commented on GitHub (Dec 12, 2024): This is a similar issue, but I was asked to open a new one for this use case specifically.
Author
Owner

@bctiemann commented on GitHub (Dec 12, 2024):

OK, I missed that context.
Marking as blocked by #17954

@bctiemann commented on GitHub (Dec 12, 2024): OK, I missed that context. Marking as blocked by #17954
Author
Owner

@github-actions[bot] commented on GitHub (Dec 20, 2024):

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.

@github-actions[bot] commented on GitHub (Dec 20, 2024): 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.
Author
Owner

@github-actions[bot] commented on GitHub (Dec 28, 2024):

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.

@github-actions[bot] commented on GitHub (Dec 28, 2024): 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.
Author
Owner

@github-actions[bot] commented on GitHub (Jan 4, 2025):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@github-actions[bot] commented on GitHub (Jan 4, 2025): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10475