Upgrade to V2.5.3 loses changelog records #2384

Closed
opened 2025-12-29 17:25:33 +01:00 by adam · 4 comments
Owner

Originally created by @CraigRMoore on GitHub (Feb 15, 2019).

We performed an upgrade from V2.4.6 -> V2.5.3 and have only just now noticed that we have lost any previous changelog records.

Steps to Reproduce

  1. Upgrade from V2.4.6 -> V2.5.3
  2. Upgrade successfully with no obvious errors reported

Changelog records to be retained

Changelog records lost

Originally created by @CraigRMoore on GitHub (Feb 15, 2019). We performed an upgrade from V2.4.6 -> V2.5.3 and have only just now noticed that we have lost any previous changelog records. ### Steps to Reproduce 1. Upgrade from V2.4.6 -> V2.5.3 2. Upgrade successfully with no obvious errors reported 3. <!-- What did you expect to happen? --> ## Changelog records to be retained <!-- What happened instead? --> Changelog records lost
adam closed this issue 2025-12-29 17:25:34 +01:00
Author
Owner

@stuntguy3000 commented on GitHub (Feb 15, 2019):

Both versions you stated are now outdated and probably unsupported. I did an upgrade from 2.5.5->2.5.6 last night no worries.

Did you run the migration script?

@stuntguy3000 commented on GitHub (Feb 15, 2019): Both versions you stated are now outdated and probably unsupported. I did an upgrade from 2.5.5->2.5.6 last night no worries. Did you run the migration script?
Author
Owner

@CraigRMoore commented on GitHub (Feb 15, 2019):

ok, assuming you mean the upgrade.sh script? then yes.

@CraigRMoore commented on GitHub (Feb 15, 2019): ok, assuming you mean the upgrade.sh script? then yes.
Author
Owner

@stuntguy3000 commented on GitHub (Feb 15, 2019):

I can't comment on schema changes from 2.4 -> 2.5 so you will have to sit tight until another contributor can comment.

@stuntguy3000 commented on GitHub (Feb 15, 2019): I can't comment on schema changes from 2.4 -> 2.5 so you will have to sit tight until another contributor can comment.
Author
Owner

@jeremystretch commented on GitHub (Feb 15, 2019):

Thank you for your interest in NetBox. GitHub issues are intended for reporting reproducible bugs and requesting features, and must be submitted using one of the templates provided here. For general discussion, questions, or assistance with installation issues, please post to our mailing list instead.

@jeremystretch commented on GitHub (Feb 15, 2019): Thank you for your interest in NetBox. GitHub issues are intended for reporting reproducible bugs and requesting features, and must be submitted using one of the templates provided [here](https://github.com/digitalocean/netbox/issues/new/choose). For general discussion, questions, or assistance with installation issues, please post to our [mailing list](https://groups.google.com/forum/#!forum/netbox-discuss) instead.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2384