Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade from 2.2.9 to 2.3.0 fails - DB error #1933

Closed
CDawson1 opened this issue Mar 1, 2018 · 5 comments
Closed

Upgrade from 2.2.9 to 2.3.0 fails - DB error #1933

CDawson1 opened this issue Mar 1, 2018 · 5 comments

Comments

@CDawson1
Copy link

CDawson1 commented Mar 1, 2018

Issue Type

[x ] Bug report

Environment

  • Python version: 2.7.12
  • NetBox version: 2.2.9

Description

Unable to upgrade to 2.3.0

I've run across this issue somewhere here yesterday as a known issue, but for whatever reason, I cannot for the life of me find it now, so please feel free to whack this with a referral to the other thread.

In short, I'm unable to upgrade from 2.2.9 to 2.3.0. I'm met with a server/DB error.

netboxerror

And running the suggested steps yields no positive result. For the record, PostgreSQL is 9.5.10.

@jeremystretch
Copy link
Member

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

@CDawson1
Copy link
Author

CDawson1 commented Mar 1, 2018

This is a bug...following your steps to upgrade, (here) that's the error. This is not an installation assistance request...

In addition, as mentioned, this exists elsewhere here, just can't find it at the moment, hence the request to link that issue.

@lae
Copy link
Contributor

lae commented Mar 1, 2018

Are you talking about #1892? That's a different issue (that was fixed prior to release).

@CDawson1
Copy link
Author

CDawson1 commented Mar 2, 2018

Nope. Let me dig a little more.

@CDawson1
Copy link
Author

CDawson1 commented Mar 6, 2018

Cannot for the life of me find it anymore. Must have been an alternate reality. But the reality of this is following the documentation verbatim, the upgrade fails.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants