-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Closed
Labels
Azure CLI TeamThe command of the issue is owned by Azure CLI teamThe command of the issue is owned by Azure CLI teamcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues 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 thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone
Description
Describe the bug
Trying to install azure-cli from the official repo. This works fine for noble, but when I try with jammy I get the following error:
$ apt update
…
Ign:14 https://packages.microsoft.com/repos/azure-cli jammy InRelease
Err:14 https://packages.microsoft.com/repos/azure-cli jammy InRelease
Bad header line Bad header data [IP: 2620:1ec:bdf::54 443]
Fetched 5.654 B in 7s (755 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
W: Failed to fetch https://packages.microsoft.com/repos/azure-cli/dists/jammy/InRelease Bad header line Bad header data [IP: 2620:1ec:bdf::54 443]
$ cat /etc/apt/sources.list.d/azure-cli.sources
Types: deb
URIs: https://packages.microsoft.com/repos/azure-cli/
Suites: jammy
Components: main
Architectures: amd64
Signed-by: /etc/apt/keyrings/microsoft.asc
Related command
apt update
Errors
Failed to fetch https://packages.microsoft.com/repos/azure-cli/dists/jammy/InRelease Bad header line Bad header data [IP: 2620:1ec:bdf::54 443]
Issue script & Debug output
N/A
Expected behavior
N/A
Environment Summary
azure-cli 2.65.0
Additional context
No response
Metadata
Metadata
Assignees
Labels
Azure CLI TeamThe command of the issue is owned by Azure CLI teamThe command of the issue is owned by Azure CLI teamcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues 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 thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that