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
[bug] [question] apt reports changed origin to 'Pulp 3' ? at htttp://packages.microsoft.com/repos/code #96
Comments
@razielanarki thanks for the bug report. Looks like this is a bug and we should have a fix out shortly. Apologies. |
On my PC with Ubuntu I unfortunately accepted the change proposed by APT: is there any security implications? Can I rest assured? |
@Teo80 there's not a security implication per se, the repo signatures are your safeguard against that. But you'll have to accept the change again when the fields go back to their expected value (which we're actively working to fix). |
The fix has been implemented, and all affected repos have been re-published to correct the Origin and Label fields. |
I'm still experiencing this issue on Ubuntu 22.04.3 LTS. When downloading the InRelease file manually it still says: Origin: Pulp 3 |
Also still have the issue, Debian Bullseye (cleaned all metadata) |
@mbearup - right, it is correct now; maybe just some CDN/caching issues. |
Could you confirm which repos you're trying to sync? I tried our Ubuntu 22.04, Debian 11, and code repos, and I see the correct origin/label reflected in each
|
I saw the same issue just now, but a 2nd run worked so some CDN wonkyness still. that was http://packages.microsoft.com/repos/code/dists/stable/InRelease |
I am having the same issue still:
|
@Silvergti could you confirm which IP you're hitting for packages.microsoft.com? I no longer see the issue repro'ing, but I can check if there's an issue with an individual mirror. |
|
@Silvergti when I pull the metadata from that mirror, I see the correct values. If you're still seeing the issue, it may be due to layers of caching along your network path.
|
Hello @mbearup That might have been the case, indeed. I am getting the same as you (never ran this when it wasn't working):
Re-tried again and it is working now. Thanks! |
This is the resource apt tries to load
Clearing the apt cache worked. Thanks! |
@chr1s-code can you confirm which IP address you're hitting? I can no longer repro, but glad to check an individual mirror if you still see the issue. |
This command solves the problem on local machine: sudo apt-get clean |
Just run into the bug. sudo apt-get clean didn't help. |
@romansh can you tell us what repo you're attempting to use and what IP address your system resolves to for packages.microsoft.com? It's possible we have an edge node that didn't get an update. |
Same here. Debian. Messages are
|
@Janvanoorschot can you tell us what IP address packages.microsoft.com resolves to on the system with the problem? |
deb [arch=amd64,arm64,armhf] http://packages.microsoft.com/repos/code stable main ping packages.microsoft.com |
|
sudo apt-get clean Everything is working as expected now. |
There seems to be some CDN caching issues. Curl'ing the Release file twice gives different results, once valid and once invalid.
|
@Foorack @romansh @Janvanoorschot I think I have this beaten into submission for now. Starting to deploy a fix to ensure this particular CDN caching issue doesn't repeat. Thanks for your patience and for giving us the info we needed to find the issue. |
I also got the error a couple of minutes ago, but ran it again now and it's gone. Thanks for fixing it so fast. |
I have this running for some time, it is a random change in IP address, only 13.81.215.193 is wrong: I am located the the Netherlands... $ host packages.microsoft.com $ while true; do date; wget https://packages.microsoft.com/repos/code/dists/stable/InRelease -O - 2>&1 | egrep 'Resolving|Origin:'; sleep 30; done Hope this helps... |
@jasonzio problem fixed for me. Thanks! |
Thanks to all. A fix has been deployed which should prevent this from recurring. If you see this happen again, please do let us know. Again, thanks for your patience. |
Seeing this across our estate this morning, from AWS WorkSpaces Ubuntu instances which we manage with Ansible:
trying to run the fix above doesn't work:
|
@ps-spb In your case the machine has already accepted the incorrect Origin "Pulp 3", and you therefore has to accept it again to revert it back to "code stable". You can automate this via ansible with |
jasonzio would it be possible share the fix on the pulp side. As I'm having a similar issue internally :D |
@srelf-eschercloud Try setting |
Describe the issue
i may have missed an announcement?
When did the issue occur?
just now
If applicable, what package did you attempt to install, and from which repo?
Steps to Reproduce
sudo apt-get update
Actual Result
warning
Expected Result
code-insiders updated
Additional context
i am running code-insiders on ubuntu-mantic+proposed w mainline kernel 6.7.0-rc2 (self-signed)
The text was updated successfully, but these errors were encountered: