[Core] Fix #33282: az: Support Ubuntu 26.04 LTS (resolute) in deb install script

[Aditya Pujara (a0x1ab)]

🤖 PR Validation — ️✔️ All clear

Breaking Changes	Tests
️✔️ None	️✔️ 130/130

Description

Fixes #33282.

deb_install.sh hardcoded CLI_REPO="jammy" as the Ubuntu fallback, so Ubuntu 26.04 (resolute) — and any future Ubuntu release without its own package suite — silently installed from a 22.04 repo instead of the most recent supported LTS.

Changes

• scripts/release/debian/deb_install.sh

  • Cache the curl response from packages.microsoft.com/repos/azure-cli/dists/ once into AZURE_CLI_DISTS (avoids redundant network calls)
  • Replace hardcoded CLI_REPO="jammy" with a loop over noble jammy focal (newest-first); picks the first codename present in the repo; exits with the existing error if none match

  # Before
  if [[ $DIST =~ "Ubuntu" ]]; then
      CLI_REPO="jammy"
  
  # After
  if [[ $DIST =~ "Ubuntu" ]]; then
      for lts_codename in noble jammy focal; do
          if [[ $AZURE_CLI_DISTS =~ $lts_codename ]]; then
              CLI_REPO="$lts_codename"
              break
          fi
      done
      if [[ -z $CLI_REPO ]]; then
          echo "$ERROR_MSG"
          exit 1
      fi

• scripts/release/debian/test_deb_install.sh

  • Added ubuntu:noble to the base_images test array

Testing Guide

Run deb_install.sh on an Ubuntu 26.04 host (or simulate by setting lsb_release -cs to return an unknown codename on an Ubuntu distro). The script should resolve to noble (or jammy/focal if noble is absent from the repo) rather than silently using jammy.

History Notes

[Core] az: Support Ubuntu 26.04 LTS (resolute) in deb install script — fall back to newest available LTS instead of hardcoded jammy

[azure-client-tools-bot-prd]

Hi Aditya Pujara (@a0x1ab),
Since the current milestone time is less than 7 days, this pr may not catch up with this release.

[azure-client-tools-agent]

Live test skipped

⏭️ Skipping the live test for this revision because no changed test file was found (tests/**/test_*.py).

The live-test pipeline runs only the test files a PR changes, so there is nothing to execute for this commit. A skipped live test is not a passing test result. The Agent review separately checks whether the affected command module includes focused regression tests or updated recordings. If a test file is changed in a later commit, the live test will run automatically.

[azure-client-tools-agent]

Yu Chen (@jsntcy), ### Upstream CI

Azure.azure-cli

• Result: failure
• Failure details:
  • Integration Test against Profiles Python312 (Not PR-related)
    • Evidence: The job running on agent pool-ubuntu-2204 9 ran longer than the maximum time of 20 minutes.
    • This is a pipeline agent timeout unrelated to the PR's source changes (a shell-script fallback for Ubuntu LTS codename detection). No source change is requested for this failure; recommend rerunning/escalating the timed-out job to the pipeline owner.

Test validation

• Live test: Skipped: PR changes no test files (tests/**/test_*.py)
• Regression coverage: Not applicable to the changed files.

No review-skill findings.

Risk assessment

1/100 · Low · Low confidence

No additional owning-squad review signal was detected. Main signals: small, isolated diff.

[Yong Zhang (yonzhan)]

Core

[azure-client-tools-agent]

Aditya Pujara (@a0x1ab)

Upstream CI

Azure.azure-cli

• Result: failure
• Failure details:
  • Integration Test against Profiles Python312 (Not PR-related)
    • Evidence: The job running on agent pool-ubuntu-2204 9 ran longer than the maximum time of 20 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134
    • Next action: Re-run the timed-out job. If it times out again at the same setup or checkout step, escalate to the pipeline owner instead of changing unrelated PR source.
    • Verify: Re-run Integration Test against Profiles Python312 and confirm the job completes within its limit.

Test validation

• Live test: Skipped: no runnable changed test files were found.
• Regression coverage: Not applicable to the changed files.

Summary

The single CI failure is a job-level timeout on Integration Test against Profiles Python312, unrelated to this PR's change (a two-line addition to the Debian install script's supported-release list plus a matching test-script tweak). No source change is requested for this failure; recommend rerunning the timed-out job, and escalating to the pipeline owner if it continues to time out.

No review-skill findings were confirmed: the diff is scoped exactly to scripts/release/debian/deb_install.sh and scripts/release/debian/test_deb_install.sh, consistent with the PR title and description.

Risk assessment

1/100 · Low · Low confidence

No additional owning-squad review signal was detected. Main signals: small, isolated diff.

[microsoft-github-policy-service]

🔔 Routing this PR to @Azure/act-platform-engineering-squad.

[azure-client-tools-agent]

Aditya Pujara (@a0x1ab)

Upstream CI

Azure.azure-cli

• Result: failure
• Failure details:
  • Integration Test against Profiles Python312 (Not PR-related)
    • Evidence: The job running on agent pool-ubuntu-2204 9 ran longer than the maximum time of 20 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134
    • Next action: Re-run the timed-out job. If it times out again at the same setup or checkout step, escalate to the pipeline owner instead of changing unrelated PR source.
    • Verify: Re-run Integration Test against Profiles Python312 and confirm the job completes within its limit.

Test validation

• Live test: Skipped: no runnable changed test files were found.
• Regression coverage: Not applicable to the changed files.

No review-skill findings were identified for this change.

The only failing check is a job timeout (Integration Test against Profiles Python312 exceeded its 20-minute limit) unrelated to the two shell script files this PR touches. No source change is requested for this failure; recommend re-running or escalating the timed-out job to the pipeline owner.

Risk assessment

1/100 · Low · Low confidence

The Low rating reflects the detected change scope with no elevated security, reliability, customer, operational, dependency, sovereign-cloud, generated-output, or cross-component signal.

• Change scope: 2 changed files, 17 changed lines (+14 / -3), including 0 production files.
• Affected components: No production component was identified.
• Risk drivers: No elevated risk signal was detected.
• Regression evidence: No production-code regression-test signal applies.
• Confidence: Low because no production changed-line evidence was available.
• Required review: No additional owning-squad review signal was detected.