Blog Detail
With the release of Nautobot 2.1.9 and 1.6.16 came new requirements for pynautobot to include an authentication token that for some initial calls that were not previously required. So to make sure that pynautobot (and subsequently Nautobot Ansible) and Nautobot Helm Chart work with the most recent version of Nautobot, new versions have been released.
pynautobot & Nautobot Ansible
First to check what version of pynautobot you have, you can run pip list
to get that environment. Here is an example of using grep to only look for pynautobot.
❯ pip list | grep pynautobot
pynautobot 2.0.2
Nautobot 1.6 Environments
If you are continuing on the LTM release train of 1.6, your pynautobot needs to be upgraded to 1.5.2 in order to continue using the Ansible modules (4.5.0). No update to the Ansible modules is required-only the underlying pynautobot version. Complete this with:
pip install pynautobot==1.5.2
Accidental Upgrade to 2.x of pynautobot?
If you accidentally upgrade to the latest version of pynautobot but intended to be on 1.x, just issue the same command as above and you will get the right version. Nothing further would needs to be done-no harm.
pip install pynautobot=-1.5.2
Nautobot 2.1 Environments
For those with the latest Nautobot application version of 2.1.9, please upgrade the pynautobot instance in your Ansible environment to the latest of 2.1.1
pip install --upgrade pynautobot
Nautobot Helm Chart
First to check what version of Nautobot Helm Chart you have configured, you can run helm show chart nautobot/nautobot
to get the full information about the configured chart. There will be multiple versions you will see in the output, the chart version that matters is the last line in the output and is a root key in the yaml output.
❯ helm show chart nautobot/nautobot
annotations:
... Truncated for bevity ...
sources:
- https://github.com/nautobot/nautobot
- https://github.com/nautobot/helm-charts
version: 2.0.5
Warning – READ BEFORE PROCEEDING
The latest version of the helm chart has a default version for Nautobot that is set to 2.1.9, if you are NOT providing custom image or statically declaring the version you WILL
be upgraded to 2.1.9. For more information on using a custom image please see the documentation here or for using the Network to Code maintained images with a specific version please ensure nautobot.image.tag
is set to the tagged version you are expecting to use. Below are some examples for values.yaml
provided to a helm release.
If you are on a 1.X.X
version of the helm chart please review the upgrade guide here before proceeding.
Custom Image
nautobot:
image:
registry: "ghcr.io"
repository: "my-namespace/nautobot"
tag: "1.6.16-py3.11"
pullPolicy: "Always"
pullSecrets:
- ghcr-pull-secret
Network to Code Image
nautobot:
image:
tag: "1.6.16-py3.11"
Update Helm Repo
Before you can use the new version of the helm chart you must update the helm repo.
❯ helm repo update nautobot
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "nautobot" chart repository
Update Complete. ⎈Happy Helming!⎈
Update Helm Release
Now you can proceed to update your helm release with the latest helm chart version.
❯ helm upgrade <name of helm release> -f values.yml --version 2.1.0
Release "nautobot" has been upgraded. Happy Helming!
NAME: nautobot
LAST DEPLOYED: Wed Mar 27 20:09:47 2024
NAMESPACE: default
STATUS: deployed
REVISION: 3
NOTES:
*********************************************************************
*** PLEASE BE PATIENT: Nautobot may take a few minutes to install ***
*********************************************************************
... Truncated for bevity ...
Conclusion
When issues do arise on playbooks that were previously working fine, it’s best to give your dependency software packages a quick update. Hope that this helps. Happy automating.
-Josh, Jeremy
Contact Us to Learn More
Share details about yourself & someone from our team will reach out to you ASAP!