search

microsoft / linux-package-repositories

Microsoft Packaged Linux Software (DEBs, RPMs, etc) are hosted on packages.microsoft.com (PMC) made available as native Linux repositories for use with package managers like APT, YUM, etc.
https://packages.microsoft.com
MIT License
64 stars 17 forks source link

Report an issue #116

Closed tnguye45-mgl closed 6 months ago

tnguye45-mgl commented 6 months ago

Describe the issue Unable to install mssql-tools package for RHEL programmatically in AWS EC2 instance

When did the issue occur? Starting from at least 4 March 2024 at 20:44 CST

If applicable, what package did you attempt to install, and from which repo? mssql-tools from RHEL repo (URL https://packages.microsoft.com/rhel/7/prod/Packages/m/mssql-tools-17.10.1.1-1.x86_64.rpm)

Steps to Reproduce Using CloudFormation, set up code to deploy a Linux EC2 instance and as part of the build scripts use the following command: yum -y install mssql-tools

Actual Result https://packages.microsoft.com/rhel/7/prod/Packages/m/mssql-tools-17.10.1.1-1.x86_64.rpm: [Errno 14] curl#22 - "The requested URL returned error: 403"

Expected Result mssql-tools package installs successfully

Screenshots Unable to upload screenshots due to corporate network security

Additional context

mbearup commented 6 months ago

@tnguye45-mgl thanks for reporting this. If you could post the results of the following curl command, that would help us identify the issue.

curl -L -v https://packages.microsoft.com/rhel/7/prod/Packages/m/mssql-tools-17.10.1.1-1.x86_64.rpm

Two factors to consider.

  1. These SQL packages are delivered within a geofence (for tax/legal reasons) so your client will see a 302 redirect. But that shouldn't result in a 403 - modern dnf clients can easily follow the redirect.
  2. We've seen cases where auth headers in the client request can cause 403s. On the backend, these requests are served by Azure Storage, which can reject such requests because the auth headers are unrecognized. Our edge infrastructure should be stripping these headers, but perhaps there's a corner case we've missed.
tnguye45-mgl commented 6 months ago

Sorry, need to close this issue as we believe it's something on our side, and to prevent further comments on this issue