The worst part is that they marked the incident as resolved after 32 minutes, but didn't mention that mirrors for the packages on security.ubuntu.com have huge queues. OK fine, we can wait until the mirrors sync and you can choose another mirror to do your update - eventually. You can also work around this while updating Ubuntu 24.04 by manually installing the deb file it wants.
But wait, there's more! You can't install new instances of Ubuntu 24.04.2 because the installer connects to security.ubuntu.com by default (probably for good reasons) and will bail out while formatting and writing the disk when it gets 500 Internal Server Error from security.ubuntu.com for a specific deb file. There's no option around it that I'm aware of if you're doing an install connected to the network. I'm told that things should work if you try to install without networking connected. But that's not working for me, possibly due to some drivers it needs to pull for my hardware that are not in the default installer.
Ran into this while trying to install a fresh instance on an old mac hardware.
All in all, not a good look for Canonical, especially given how long this is taking to resolve and the lack of any status indication that this is still a problem. Lots of people are being bitten by this in the last 24 hours.
2 comments
[ 2.7 ms ] story [ 30.7 ms ] threadBut wait, there's more! You can't install new instances of Ubuntu 24.04.2 because the installer connects to security.ubuntu.com by default (probably for good reasons) and will bail out while formatting and writing the disk when it gets 500 Internal Server Error from security.ubuntu.com for a specific deb file. There's no option around it that I'm aware of if you're doing an install connected to the network. I'm told that things should work if you try to install without networking connected. But that's not working for me, possibly due to some drivers it needs to pull for my hardware that are not in the default installer.
Ran into this while trying to install a fresh instance on an old mac hardware.
All in all, not a good look for Canonical, especially given how long this is taking to resolve and the lack of any status indication that this is still a problem. Lots of people are being bitten by this in the last 24 hours.
https://discourse.ubuntu.com/t/problem-with-updates-error-fa...