Fix default package list for upgrade workflow #33
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to the way the package dependencies are structured, trying to upgrade to a new driver branch with the Canonical packages currently fails.
For example, if we install the 450 driver branch with DeepOps, and then try to run the playbook again with
nvidia_driver_ubuntu_branch: 460
, we see an error like this:Adding
nvidia-headless-no-dkms-{{ nvidia_driver_ubuntu_branch }}-server
to the list of packages we specify explicitly as part of the install appears to resolve the issue. The playbook runs successfully, and when we check the package list it shows all packages are in the new driver branch (460). (Note that all450
packages are inrc
state)