Skip to content

Focal arm64 apt repo down #32889

@pelmers-db

Description

@pelmers-db

Describe the bug

The focal arm64 apt repo is returning 502 errors.

Related command

To repro, on an arm64 focal machine:

$ sudo apt update
$ sudo apt install azure-cli
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  apport-symptoms liblockfile-bin liblockfile1 python3-cliapp python3-markdown python3-systemd python3-ttystatus ssl-cert
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
  azure-cli
0 upgraded, 1 newly installed, 0 to remove and 58 not upgraded.
Need to get 53.9 MB of archives.
After this operation, 708 MB of additional disk space will be used.
Err:1 https://packages.microsoft.com/repos/azure-cli focal/main arm64 azure-cli arm64 2.72.0-1~focal
  Connection failed [IP: 13.107.213.52 443]
E: Failed to fetch https://packages.microsoft.com/repos/azure-cli/pool/main/a/azure-cli/azure-cli_2.72.0-1~focal_arm64.deb  Connection failed [IP: 13.107.213.52 443]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Errors

Err:1 https://packages.microsoft.com/repos/azure-cli focal/main arm64 azure-cli arm64 2.72.0-1~focal
  Connection failed [IP: 13.107.213.52 443]
E: Failed to fetch https://packages.microsoft.com/repos/azure-cli/pool/main/a/azure-cli/azure-cli_2.72.0-1~focal_arm64.deb  Connection failed [IP: 13.107.213.52 443]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Issue script & Debug output

does not apply

Expected behavior

should install

Environment Summary

not available, cannot install

Additional context

No response

Metadata

Metadata

Labels

Auto-ResolveAuto resolve by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamInstallationPossible-SolutionSimilar-Issuecustomer-reportedIssues that are reported by GitHub users external to the Azure organization.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions