Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

edge yumrepos config.repo file content conflicting protocol with port #82

Closed
bcunninghaminfor opened this issue Sep 13, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@bcunninghaminfor
Copy link

Describe the issue
Since yesterday around 1730 hours UTC, we have had failures installing edge via yum. It appears the config.repo file (https://packages.microsoft.com/yumrepos/edge/config.repo) has conflicting protocol and port. Possibly should be https

When did the issue occur?
September 12 around 1730 hours UTC

If applicable, what package did you attempt to install, and from which repo?
yum microsoft-edge-stable

Steps to Reproduce
rpm --import https://packages.microsoft.com/keys/microsoft.asc && curl https://packages.microsoft.com/yumrepos/edge/config.repo > /etc/yum.repos.d/microsoft-edge-dev.repo && yum --nogpgcheck install -y microsoft-edge-stable

Actual Result
http://packages.microsoft.com:443/yumrepos/edge/repodata/repomd.xml: [Errno 14] HTTP Error 400 - Bad Request
Trying other mirror.

Expected Result
Successful package install

Screenshots
image

Additional context
Our script has not changed and we noticed microsoft-edge-stable-116.0.1938.81-1.x86_64.rpm was uploaded at September 12 1722 hours UTC but the repodata directory was updated at 1858 hours UTC. We had a successful install in between these times.

@bcunninghaminfor bcunninghaminfor added the bug Something isn't working label Sep 13, 2023
@daviddavis
Copy link
Member

Thanks for filing this issue. The protocol is indeed wrong (should be https). We're working on a fix.

@daviddavis
Copy link
Member

https://packages.microsoft.com/yumrepos/edge/config.repo should be fixed now. We're clearing other config.repo files from our cache as well.

@sdherr
Copy link
Contributor

sdherr commented Sep 13, 2023

All affected config.repo files / regions have been purged, this issue should be completely resolved.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants