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

config context not applied on devices when using tag filter on cluster object #8761

New Issue
Closed
opened 2025-12-29 20:40:53 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:40:53 +01:00
Owner
Copy Link

Originally created by @soofff on GitHub (Oct 19, 2023).

NetBox version

v3.5.8

Python version

3.8

Steps to Reproduce

  1. create cluster and (create+) assign hosts
  2. create/assign tag to cluster e.g. TAG1
  3. create config context and assign TAG1

Expected Behavior

i would expect that the config context is assigned to all devices where the cluster(s) have the assigned tag.
when i use cluster assignment instead of tags, everything works as expected.

Observed Behavior

no config context is rendered/shown on the device which are a part of the tagged cluster.

Originally created by @soofff on GitHub (Oct 19, 2023). ### NetBox version v3.5.8 ### Python version 3.8 ### Steps to Reproduce 1. create cluster and (create+) assign hosts 2. create/assign tag to cluster e.g. `TAG1` 3. create config context and assign `TAG1` ### Expected Behavior i would expect that the config context is assigned to all devices where the cluster(s) have the assigned tag. when i use cluster assignment instead of tags, everything works as expected. ### Observed Behavior no config context is rendered/shown on the device which are a part of the tagged cluster.
adam closed this issue 2025-12-29 20:40:54 +01:00
adam commented 2025-12-29 20:40:54 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 19, 2023):

Config contexts consider only tags which are assigned directly to a device or virtual machine. They intentionally don't consider tags which are applied to the cluster in which a VM is assigned, as that could be very difficult to manage at scale.

Instead, you can either apply the tags directly to the desired VM, or associate the config context with the appropriate cluster(s). Hope that helps!

@jeremystretch commented on GitHub (Oct 19, 2023): Config contexts consider only tags which are assigned directly to a device or virtual machine. They intentionally don't consider tags which are applied to the cluster in which a VM is assigned, as that could be very difficult to manage at scale. Instead, you can either apply the tags directly to the desired VM, or associate the config context with the appropriate cluster(s). Hope that helps!
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
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#8761
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?