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

Unable to update secrets #3922

New Issue
Closed
opened 2025-12-29 18:32:06 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:32:06 +01:00
Owner
Copy Link

Originally created by @joaolucasmacedo on GitHub (Jul 30, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.6
  • NetBox version: 2.8.8

I'm trying to update some device secrets ant it shows an error. I had to delete the secret and create a new one.
By the way, would be nice to return to the original device page after delete a secret, instead of secrets page.

Steps to Reproduce

  1. Select device secret.
  2. Click "Edit".
  3. Chage password and click "Update".

Expected Behavior

Update password.

Observed Behavior

Error popup: "Each secret assigned to a device must have a unique combination of role and name"

Originally created by @joaolucasmacedo on GitHub (Jul 30, 2020). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.6 * NetBox version: 2.8.8 I'm trying to update some device secrets ant it shows an error. I had to delete the secret and create a new one. By the way, would be nice to return to the original device page after delete a secret, instead of secrets page. ### Steps to Reproduce 1. Select device secret. 2. Click "Edit". 3. Chage password and click "Update". ### Expected Behavior Update password. <!-- What happened instead? --> ### Observed Behavior Error popup: "Each secret assigned to a device must have a unique combination of role and name"
adam added the type: bugstatus: accepted labels 2025-12-29 18:32:06 +01:00
adam closed this issue 2025-12-29 18:32:06 +01:00
adam commented 2025-12-29 18:32:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 30, 2020):

This is a regression introduced in edf15532d2 for #4702

@jeremystretch commented on GitHub (Jul 30, 2020): This is a regression introduced in edf15532d25ab94e5e92827f098d6418b8d5be96 for #4702
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 status: accepted type: bug
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#3922
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?