Upgrade from 3.7.8 to 4.0.3 failed due to missing tables #9805

Closed
opened 2025-12-29 21:22:57 +01:00 by adam · 8 comments
Owner

Originally created by @kareemshayeb on GitHub (Jun 6, 2024).

I am currently in the process of upgrading our Netbox server from version v3.7.8 to the latest release v4.0.3. During the migration phase, I encountered an inconsistency within the database.
Specifically, the extras_customfield_object_types table seems to be missing. Upon further inspection, I confirmed the presence of the following tables related to custom fields:

  • public.extras_customfield
  • public.extras_customfieldchoiceset
  • public.extras_customfield_content_types
Originally created by @kareemshayeb on GitHub (Jun 6, 2024). I am currently in the process of upgrading our Netbox server from version v3.7.8 to the latest release v4.0.3. During the migration phase, I encountered an inconsistency within the database. Specifically, the extras_customfield_object_types table seems to be missing. Upon further inspection, I confirmed the presence of the following tables related to custom fields: - public.extras_customfield - public.extras_customfieldchoiceset - public.extras_customfield_content_types
adam closed this issue 2025-12-29 21:22:57 +01:00
Author
Owner

@jeffgdotorg commented on GitHub (Jun 6, 2024):

Hi @kareemshayeb, I'm the product manager for NetBox Open Source.

We noticed that this issue does not follow any of the project's issue templates. We think that's because it was created via a Slack integration. Can you please confirm that guess?

@jeffgdotorg commented on GitHub (Jun 6, 2024): Hi @kareemshayeb, I'm the product manager for NetBox Open Source. We noticed that this issue does not follow any of the project's [issue templates](https://github.com/netbox-community/netbox/issues/new/choose). We think that's because it was created via a Slack integration. Can you please confirm that guess?
Author
Owner

@kareemshayeb commented on GitHub (Jun 6, 2024):

Yes, that's correct. That was using the Slack.

@kareemshayeb commented on GitHub (Jun 6, 2024): Yes, that's correct. That was using the Slack.
Author
Owner

@DanSheps commented on GitHub (Jun 6, 2024):

This issue is being closed as it does not conform to one of the provided templates as required by the contributing guide. If you'd like to request that your issue be re-opened, please first update the content so that it matches the appropriate template (this may require rewriting your issue entirely).

@DanSheps commented on GitHub (Jun 6, 2024): This issue is being closed as it does not conform to one of the [provided templates](https://github.com/netbox-community/netbox/issues/new/choose) as required by the [contributing guide](https://github.com/netbox-community/netbox/blob/master/CONTRIBUTING.md). If you'd like to request that your issue be re-opened, please first update the content so that it matches the appropriate template (this may require rewriting your issue entirely).
Author
Owner

@jeffgdotorg commented on GitHub (Jun 6, 2024):

@kareemshayeb did you create this issue via the NetDev Slack workspace? Or a different workspace?

@jeffgdotorg commented on GitHub (Jun 6, 2024): @kareemshayeb did you create this issue via the NetDev Slack workspace? Or a different workspace?
Author
Owner

@kareemshayeb commented on GitHub (Jun 7, 2024):

yes, via NetDev Community.

@kareemshayeb commented on GitHub (Jun 7, 2024): yes, via NetDev Community.
Author
Owner

@jeffgdotorg commented on GitHub (Jun 7, 2024):

@kareemshayeb do you recall from which channel and by which command you were able to make this issue?

@jeffgdotorg commented on GitHub (Jun 7, 2024): @kareemshayeb do you recall from which channel and by which command you were able to make this issue?
Author
Owner

@kareemshayeb commented on GitHub (Jun 7, 2024):

@jeffgdotorg Here is the link to the original question that I've posted. In addition to the menu and option of creating the Github issue.

issue

I already created a question instead on an issue in the discussions area. Is there the right place for it? I hope to get an answer since this issue is preventing me from upgrading to the new major release.
Thanks.

@kareemshayeb commented on GitHub (Jun 7, 2024): @jeffgdotorg Here is [the link](https://netdev-community.slack.com/archives/C01P0FRSXRV/p1717658234803609) to the original question that I've posted. In addition to the menu and option of creating the Github issue. ![issue](https://github.com/netbox-community/netbox/assets/39455431/85287fb8-9dd8-480f-87ed-3e2edc9e1c80) I already created [a question](https://github.com/netbox-community/netbox/discussions/16441) instead on an issue in the discussions area. Is there the right place for it? I hope to get an answer since this issue is preventing me from upgrading to the new major release. Thanks.
Author
Owner

@jeffgdotorg commented on GitHub (Jun 7, 2024):

Thanks for helping me solve a mystery.

You created the discussion in the right place. I'll see if I can draw some attention to it.

@jeffgdotorg commented on GitHub (Jun 7, 2024): Thanks for helping me solve a mystery. You created the discussion in the right place. I'll see if I can draw some attention to it.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9805