Is the latest – and already a downgrade which I did as I thought maybe I backed myself into a dead end there.
Did I do something wrong to end up in a bad state with my update? As I said: You guys do an amazing job rolling out regular updates, so it probably is something I did.
A status page for possible service problems on build and updates would be immensely helpful, to be honest. Nothing automatic, just something that says No known service problems or Builds on Bluefin paused for the following reason, plus the date that it was posted. Again, it does not need to be fancy at all, but it’s much better than a user posting here or receiving the answer check the actions on GitHub, when most users have no idea what GitHub even is. Something simple based on Kuma, like this example status.plex.tv, is more than sufficient in my opinion.
The build failures are transparent to you, it doesn’t matter to you unless it’s a long time. If we had to do an update every time a build failed we would spend all of our time posting updates.
If you care about build failures then learn to use Github, that’s what I do.
Sorry I wasn’t clear at all in my request. My fault. Obviously, a build failure does not warrant a status page. What I meant in my recommendation was simply a page that states whether there is a service problem or not. The page would typically show a “systems fully operational” message in green 99.99% of the time, but in the rare instance of a widespread issue, for example, with the update service, such a page would provide a simple and clear message to users that the error they are seeing in their terminal when they are running the system update shortcut is expected and that they simply need to be patient until the service error is resolved.
EDIT: More seriously the datacenter move is an outlier of a circumstance, they’re physically moving Fedora infra from one datacenter to another, it’s a multi day effort.
