You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The terraform feature fails on Ubuntu 26.04 ("Resolute Raccoon") with No valid OpenPGP data found. Ubuntu Noble and Debian Trixie already use a newer GPG key/repo format via NEW_GPG_CODENAMES, but resolute was missing from that list and fell back to the incompatible legacy path.
Changes
src/terraform/install.sh: Add resolute to NEW_GPG_CODENAMES so the new GPG repo setup path is used on Ubuntu 26.04; update related comments.
# This is because ubuntu noble, ubuntu resolute and debian trixie don't support the old format of GPG keys and validation
NEW_GPG_CODENAMES="trixie noble resolute"
test/terraform/scenarios.json: Add install_in_ubuntu_resolute and install_in_ubuntu_resolute_sentinel scenarios against the ubuntu:resolute image (matching the image-tag convention used by other features).
test/terraform/install_in_ubuntu_resolute.sh / install_in_ubuntu_resolute_sentinel.sh: New test scripts mirroring the noble equivalents, omitting the vscode user check since the plain ubuntu:resolute image has no such user.
Notes
ubuntu:26.04 reports VERSION_CODENAME=resolute; with this change the detection logic sets IS_GPG_NEW=1, activating the workaround.
@copilot Can you use mcr.microsoft.com/devcontainers/base:resolute base images for resolute tests instead of ubuntu:resolute? The current base image appears to have utilities missing.
@copilot Can you use mcr.microsoft.com/devcontainers/base:resolute base images for resolute tests instead of ubuntu:resolute? The current base image appears to have utilities missing.
Switched both resolute scenarios to mcr.microsoft.com/devcontainers/base:resolute and restored the vscode user check in the test scripts to match the noble tests. Done in 5cb8a68.
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
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.
The
terraformfeature fails on Ubuntu 26.04 ("Resolute Raccoon") withNo valid OpenPGP data found. Ubuntu Noble and Debian Trixie already use a newer GPG key/repo format viaNEW_GPG_CODENAMES, butresolutewas missing from that list and fell back to the incompatible legacy path.Changes
src/terraform/install.sh: AddresolutetoNEW_GPG_CODENAMESso the new GPG repo setup path is used on Ubuntu 26.04; update related comments.test/terraform/scenarios.json: Addinstall_in_ubuntu_resoluteandinstall_in_ubuntu_resolute_sentinelscenarios against theubuntu:resoluteimage (matching the image-tag convention used by other features).test/terraform/install_in_ubuntu_resolute.sh/install_in_ubuntu_resolute_sentinel.sh: New test scripts mirroring the noble equivalents, omitting thevscodeuser check since the plainubuntu:resoluteimage has no such user.Notes
ubuntu:26.04reportsVERSION_CODENAME=resolute; with this change the detection logic setsIS_GPG_NEW=1, activating the workaround.