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
nautobot:1.3.10-py3.9 ---> ff1962d125a0 (v1.4.3) in GUI #2471
Comments
Thanks for the report @telescope40. We've run across this before. Are you installing any plugins in your Docker compose files? |
Yes I am . These pre-existed prior to the issue. The upgrade was in an effort to onboard the BGP & Firewall plugins both of which seemed to result in the image being unstable. The have been removed entirely from the plugin requirements and config
|
Can you share your plugin requirements file? I assume you're using: https://github.com/nautobot/nautobot-docker-compose |
@bryanculver you can assign me on this. |
Stems from the Nautobot Golden Config plugin, that needs to be pinned to a version that does not require >1.4.0 of Nautobot. https://github.com/nautobot/nautobot-plugin-golden-config/blob/develop/pyproject.toml#L37 |
The latest version of Golden Config has requirements to use features introduced in 1.4 for a particular feature. To pin back to the previous release, change the requirements file (
|
If we can confirm this is using https://github.com/nautobot/nautobot-docker-compose then this should be addressed via nautobot/nautobot-docker-compose#50 |
Yes , I am using the Docker-Compose and replacing with nautobot-golden-config=1.1.3 does bring the build back down to 1.2.8. I am curious however , I did read the docker-compose will build the latest stable build but the image that is running 1.3.10. Anyway thanks for the quick help ! |
An interesting follow up. When I reviewing one of the objects I am prompted with . I have reverted back to 1.2.8 `A database programming error was detected while processing this request. Common causes include the following: Database migrations missing - When upgrading to a new Nautobot release, the upgrade script must be run to apply any new database migrations. You can run migrations manually by executing nautobot-server migrate from the command line. Unsupported PostgreSQL version - Ensure that PostgreSQL version 9.6 or higher is in use. You can check this by connecting to the database using Nautobot's credentials and issuing a query for SELECT VERSION().` |
@telescope40 This may have been due to migrations being applied when the container upgraded to 1.4.3. Can you perform |
See the nautobot-server migrations below , how would I check the django_migrations ? Should I just upgrade to the db to 9.6?
|
Thank you for taking the time to help me with these issues. |
Not a problem! So the migrations seem to be in line with the stated |
|
@telescope40 Looking at that output there are many migrations that were applied when you started up Nautobot with 1.4. Quick way to tell is the dates but starting at |
Related: #2653 |
Environment
Steps to Reproduce
Expected Behavior
Nautobot version 1.3.10 not 1.4.3
Observed Behavior
The text was updated successfully, but these errors were encountered: