chore: set vault to 2.0 as default version#885
Merged
Conversation
Set the default Vault channel to 2.0 and update upgrade-test fixtures to use a supported manifest channel. Assisted-By: Codex (gpt-5-5)
himax16
approved these changes
Jul 16, 2026
Raven-182
approved these changes
Jul 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR sets the default version of Vault to 2.0/stable, the supported LTS version of the 26.04 cycle.
QA steps
I've followed all these following documentations, and was able to successfully use secrets, vTPM, vTPM live migration (2026.1 new feature), and use tls certificates signed by Vault 2.0
https://canonical-openstack.readthedocs-hosted.com/en/latest/how-to/features/vault/
https://canonical-openstack.readthedocs-hosted.com/en/latest/how-to/features/secrets/
https://canonical-openstack.readthedocs-hosted.com/en/latest/how-to/misc/configuring-vtpm/
https://canonical-openstack.readthedocs-hosted.com/en/latest/how-to/features/managing-tls/tls-vault/
I have also tested refresh procedure on Vault on same track but different revisions.
Links
Jira card: OPEN-4629