starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Module Bay description missing on device #6096

New Issue
Closed
opened 2025-12-29 19:36:44 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:36:44 +01:00
Owner
Copy Link

Originally created by @michaelklose on GitHub (Feb 15, 2022).

NetBox version

v3.2.0-beta1

Python version

3.8

Steps to Reproduce

Issue is reproducible on https://beta-demo.netbox.dev/

  1. Create device type with one module bay. Module bay should have name and description configured
  2. Create new device based on the created device type

Expected Behavior

Module bay on device should have the same description as module bay on the device type.

Observed Behavior

Module bay description on the device is empty.

Originally created by @michaelklose on GitHub (Feb 15, 2022). ### NetBox version v3.2.0-beta1 ### Python version 3.8 ### Steps to Reproduce Issue is reproducible on https://beta-demo.netbox.dev/ 1. Create device type with one module bay. Module bay should have name and description configured 2. Create new device based on the created device type ### Expected Behavior Module bay on device should have the same description as module bay on the device type. ### Observed Behavior Module bay description on the device is empty.
adam added the beta label 2025-12-29 19:36:44 +01:00
adam closed this issue 2025-12-29 19:36:45 +01:00
adam commented 2025-12-29 19:36:45 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 16, 2022):

Module bay description on the device is empty.

This is intended behavior, and replicates the existing behavior for device bays and other components. The description applied to the component template is for the device type, whereas the description field on the individual component instances is intended to apply to those specific objects. For example, you might set a description of "Second line card" on the module bay template, but might use the description on a module bay instance to note an issue with a particular bay (e.g. "Card is stuck - do not use").

@jeremystretch commented on GitHub (Feb 16, 2022): > Module bay description on the device is empty. This is intended behavior, and replicates the existing behavior for device bays and other components. The description applied to the component template is for the device _type_, whereas the description field on the individual component instances is intended to apply to those specific objects. For example, you might set a description of "Second line card" on the module bay template, but might use the description on a module bay instance to note an issue with a particular bay (e.g. "Card is stuck - do not use").
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label beta
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6096
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?