netbox and netbox-rq services fail after upgrade to v3.6.0. #13637
Replies: 3 comments 4 replies
-
This suggests that your copy of How have you installed NetBox? If using |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the input. /opt/netbox/netbox/dcim/choices.py is a file that we have customized, so I run "git stash" before the upgrade to save those custom changes and then "git stash pop" to restore it after the upgrade. Normally we don't have any problems with that process, but it's possible that it became corrupted at some point. Here are the steps that we use for all upgrades:
I have already restored our instance back to v3.5.8 from a snapshot, but can try again and see what "git status" shows. Thanks. |
Beta Was this translation helpful? Give feedback.
-
Many field choices can be customized in the config. What are you customizing? Keep in mind, customizing outside the bounds of what you can do in the config file is a "do it at your own risk" and you are responsible for maintaining what is essentially a fork.
This is likely where the merge conflict comes from. When you pop the stash it should tell you of conflicts and you need to resolve those. |
Beta Was this translation helpful? Give feedback.
-
|
We modified the choices.py file to include another device status: class DeviceStatusChoices(ChoiceSet): If there is a better way to do that via the config, then I'm definitely willing to do it that way. That was just the only way that we could find to add that at the time. I can run the upgrade again with the |
Beta Was this translation helpful? Give feedback.
-
|
Ah man, there is a better way to do that
https://demo.netbox.dev/static/docs/configuration/data-validation/#field_choices
—
Mark Tinberg ***@***.***>
Division of Information Technology-Network Services
University of Wisconsin-Madison
…________________________________
From: cryansharp ***@***.***>
Sent: Friday, September 1, 2023 9:25 AM
To: netbox-community/netbox ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [netbox-community/netbox] netbox and netbox-rq services fail after upgrade to v3.6.0. (Discussion #13637)
We modified the choices.py file to include another device status:
class DeviceStatusChoices(ChoiceSet):
key = 'Device.status'
STATUS_OFFLINE = 'offline'
STATUS_ACTIVE = 'active'
STATUS_PLANNED = 'planned'
STATUS_STAGED = 'staged'
STATUS_FAILED = 'failed'
STATUS_INVENTORY = 'inventory'
STATUS_DECOMMISSIONING = 'decommissioning'
**STATUS_LOST = 'lost'**
CHOICES = [
(STATUS_OFFLINE, 'Offline', 'gray'),
(STATUS_ACTIVE, 'Active', 'green'),
(STATUS_PLANNED, 'Planned', 'cyan'),
(STATUS_STAGED, 'Staged', 'blue'),
(STATUS_FAILED, 'Failed', 'red'),
(STATUS_INVENTORY, 'Inventory', 'purple'),
(STATUS_DECOMMISSIONING, 'Decommissioning', 'yellow'),
**(STATUS_LOST, 'Lost', 'orange'),**
]
If there is a better way to do that via the config, then I'm definitely willing to do it that way. That was just the only way that we could find to add that at the time.
I can run the upgrade again with the git stash pop to see what conflicts are shown and resolve them. Thanks.
—
Reply to this email directly, view it on GitHub<#13637 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAS7UM6BVSSNJHUHRKHNCR3XYHV5NANCNFSM6AAAAAA4GFEL7A>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
See the documentation for FIELD_CHOICES. I have the following in my config: |
Beta Was this translation helpful? Give feedback.
-
|
Thank you both! That worked and I was able to successfully restart the services after the upgrade. The additional fields are also still there. Thanks again. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I upgraded our Netbox instance from v3.5.8 to v3.6.0 on a CentOS 7.9 server using the standard upgrade instructions and it was completed successfully. However, when restarting the netbox and netbox-rq services, they both fail with the following errors.
Nothing else was changed to my knowledge. I don't see any changes in the release notes that would cause this in my opinion. Has anyone encountered this before? Thanks.
Beta Was this translation helpful? Give feedback.
All reactions