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

Bug with Devices tags filter #4114

New Issue
Closed
opened 2025-12-29 18:33:13 +01:00 by adam · 10 comments
adam commented 2025-12-29 18:33:13 +01:00
Owner
Copy Link

Originally created by @gaussk32 on GitHub (Sep 18, 2020).

Environment

  • Python version: 3.8.2
  • NetBox version: 2.9.3

We have upgraded our netbox from version 2.8.3 to 2.9.3
we found a problem with the tags filter on devices section,
when you try to search filtering by a previously created tag, the drop down menu do not show any tags so, i cannot search by tag even when the tag exist.

Steps to Reproduce

  1. Upgrade the system with system from version 2.8.3 to 2.9.3

Expected Behavior

To show the tags on the filter tags of devices section in order to search by tag.

Observed Behavior

The tags created before the migration are not shown in the drop down menu tags filter of devices section.

Originally created by @gaussk32 on GitHub (Sep 18, 2020). ### Environment * Python version: 3.8.2 * NetBox version: 2.9.3 We have upgraded our netbox from version 2.8.3 to 2.9.3 we found a problem with the tags filter on devices section, when you try to search filtering by a previously created tag, the drop down menu do not show any tags so, i cannot search by tag even when the tag exist. ### Steps to Reproduce 1. Upgrade the system with system from version 2.8.3 to 2.9.3 ### Expected Behavior To show the tags on the filter tags of devices section in order to search by tag. ### Observed Behavior The tags created before the migration are not shown in the drop down menu tags filter of devices section.
adam closed this issue 2025-12-29 18:33:13 +01:00
adam commented 2025-12-29 18:33:14 +01:00
Author
Owner
Copy Link

@exiz01 commented on GitHub (Sep 18, 2020):

Same with 2.9.2, it is like no tags were imported from the previous version, it only shows tags created after upgrade.

@exiz01 commented on GitHub (Sep 18, 2020): Same with 2.9.2, it is like no tags were imported from the previous version, it only shows tags created after upgrade.
adam commented 2025-12-29 18:33:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 21, 2020):

Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v2.9.3. Note that the dropdown list in the search form shows only tags which have been applied to one or more devices.

If you believe a bug is present, please provide a detailed list of the steps someone else can take to reproduce the observed behavior, beginning with the population of tags in a v2.8 instance.

@jeremystretch commented on GitHub (Sep 21, 2020): Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v2.9.3. Note that the dropdown list in the search form shows only tags which have been applied to one or more devices. If you believe a bug is present, please provide a detailed list of the steps someone else can take to reproduce the observed behavior, beginning with the population of tags in a v2.8 instance.
adam commented 2025-12-29 18:33:14 +01:00
Author
Owner
Copy Link

@gaussk32 commented on GitHub (Sep 22, 2020):

i have upgraded from version 2.8.3 to 2.9.3 and after the migration all the previosly created and already assigned tags were not migrated, so all the tags i had in version 2.8.3 dont exist after the migration.

@gaussk32 commented on GitHub (Sep 22, 2020): i have upgraded from version 2.8.3 to 2.9.3 and after the migration all the previosly created and already assigned tags were not migrated, so all the tags i had in version 2.8.3 dont exist after the migration.
adam commented 2025-12-29 18:33:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 22, 2020):

You still need to provide explicit steps that someone else can take to reproduce the problem, beginning with the creation of the tags you believe were not migrated.

@jeremystretch commented on GitHub (Sep 22, 2020): You still need to provide explicit steps that someone else can take to reproduce the problem, beginning with the creation of the tags you believe were not migrated.
adam commented 2025-12-29 18:33:14 +01:00
Author
Owner
Copy Link

@gaussk32 commented on GitHub (Sep 22, 2020):

Step 1: you need to have installed a version 2.8.3 with many devices created and tags assigned to this devices.
Step 2: Upgrade using this manual https://netbox.readthedocs.io/en/stable/installation/upgrading/ to 2.9.3
Step 3: Once installed the new version search for one of the devices previously tagged, now the tag is lost.

If you want i could give you access with teamviewer or something, i tried to upgrade, fresh install and load the database and i got the same error.

@gaussk32 commented on GitHub (Sep 22, 2020): Step 1: you need to have installed a version 2.8.3 with many devices created and tags assigned to this devices. Step 2: Upgrade using this manual https://netbox.readthedocs.io/en/stable/installation/upgrading/ to 2.9.3 Step 3: Once installed the new version search for one of the devices previously tagged, now the tag is lost. If you want i could give you access with teamviewer or something, i tried to upgrade, fresh install and load the database and i got the same error.
adam commented 2025-12-29 18:33:14 +01:00
Author
Owner
Copy Link

@gaussk32 commented on GitHub (Sep 22, 2020):

Ok i just make a new installation
Step 1: Drop database netbox;
Step 2: rm -rf /opt/netbox
Step 3: Fresh install of netbox 2.9.3
Step 4: Create admin user
Step 5: Enter Netbox
Step 6: Load old 2.8.3 database.
Step 7: Run upgrade.sh
Step 8: Restart netbox

Following this steps the tags are not unassigned from the devices, but if i upgrade without the Step 1 and 2, just upgrade do not drop the database, the tags are deleted from the devices and from the list of tags after the upgrade.

@gaussk32 commented on GitHub (Sep 22, 2020): Ok i just make a new installation Step 1: Drop database netbox; Step 2: rm -rf /opt/netbox Step 3: Fresh install of netbox 2.9.3 Step 4: Create admin user Step 5: Enter Netbox Step 6: Load old 2.8.3 database. Step 7: Run upgrade.sh Step 8: Restart netbox Following this steps the tags are not unassigned from the devices, but if i upgrade without the Step 1 and 2, just upgrade do not drop the database, the tags are deleted from the devices and from the list of tags after the upgrade.
adam commented 2025-12-29 18:33:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 29, 2020):

Step 3: Fresh install of netbox 2.9.3
Step 4: Create admin user
Step 5: Enter Netbox
Step 6: Load old 2.8.3 database.

This workflow doesn't make sense. You can't create a user in NetBox before the database has been populated, and you can't load a database from a prior installation to an already-populated database. There's also no need to create an admin user if you're replicating a prior database which already has one.

@jeremystretch commented on GitHub (Sep 29, 2020): > Step 3: Fresh install of netbox 2.9.3 > Step 4: Create admin user > Step 5: Enter Netbox > Step 6: Load old 2.8.3 database. This workflow doesn't make sense. You can't create a user in NetBox before the database has been populated, and you can't load a database from a prior installation to an already-populated database. There's also no need to create an admin user if you're replicating a prior database which already has one.
adam commented 2025-12-29 18:33:14 +01:00
Author
Owner
Copy Link

@gaussk32 commented on GitHub (Sep 29, 2020):

Ok:
Step 1: Drop database netbox;
Step 2: rm -rf /opt/netbox
Step 3: Create postgress database.
Step 4: Fresh install of netbox 2.9.3
Step 5: Create admin user
Step 6: Enter Netbox
Step 7: Load old 2.8.3 database.
Step 8: Run upgrade.sh
Step 9: Restart netbox

Of course it make sense i created an admin user to test Netbox first if everything looks fine, then i load the old database
the error still exists i have replicated many times, what do you need to probe this bug?

@gaussk32 commented on GitHub (Sep 29, 2020): Ok: Step 1: Drop database netbox; Step 2: rm -rf /opt/netbox Step 3: Create postgress database. Step 4: Fresh install of netbox 2.9.3 Step 5: Create admin user Step 6: Enter Netbox Step 7: Load old 2.8.3 database. Step 8: Run upgrade.sh Step 9: Restart netbox Of course it make sense i created an admin user to test Netbox first if everything looks fine, then i load the old database the error still exists i have replicated many times, what do you need to probe this bug?
adam commented 2025-12-29 18:33:15 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 29, 2020):

Please see the documentation on replicating a NetBox instance for the proper procedure for restoring from a saved database. Following this process, I am not able to replicate the reported issue.

@jeremystretch commented on GitHub (Sep 29, 2020): Please see the documentation on [replicating a NetBox instance](https://netbox.readthedocs.io/en/stable/administration/replicating-netbox/) for the proper procedure for restoring from a saved database. Following this process, I am not able to replicate the reported issue.
adam commented 2025-12-29 18:33:15 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 9, 2020):

Closing due to lack of activity.

@jeremystretch commented on GitHub (Oct 9, 2020): Closing due to lack of activity.
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#4114
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?