-
Notifications
You must be signed in to change notification settings - Fork 50
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
tests(e2e): support new Azure image versioning scheme (#1039)
The Canonical CPC team recently changed the versioning scheme for Ubuntu Azure VM images from: ```json { "architecture": "x64", "offer": "0001-com-ubuntu-minimal-mantic", "publisher": "Canonical", "sku": "minimal-23_10-gen2", "urn": "Canonical:0001-com-ubuntu-minimal-mantic:minimal-23_10-gen2:23.10.202406260", "version": "23.10.202406260" } ``` To something like: ```json { "architecture": "x64", "offer": "ubuntu-24_04-lts", "publisher": "Canonical", "sku": "minimal", "urn": "Canonical:ubuntu-24_04-lts:minimal:24.04.202404230", "version": "24.04.202404230" } ``` To make matters worse, previous supported Ubuntu versions (Focal, Jammy, Mantic) still use the old version and there’s no plan to migrate them as well, thus we have to maintain both versioning schemes. Update the relevant script to differentiate between old and new codenames according to the specification above. We now require an additional `version` CLI parameter since the new versioning scheme does not use the codename at all. This is a hard requirement just for the sake of consistency, even if the previous versioning scheme does not need a version. The other main difference is that with the new versioning scheme images are Gen2 by default, while Gen1 images are explicitly noted in the SKU. Fixes UDENG-3379 ------------------ The additional commits reverse some codename-specific logic in order to add support for Oracular. Here's a run on my fork with all cells passing (including Oracular): https://github.com/GabrielNagy/adsys/actions/runs/9766528441
- Loading branch information
Showing
7 changed files
with
95 additions
and
35 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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