Re:Ubuntu 22.04 LTS servers and phased apt updates
by danw1979 on Sunday January 15, 2023 @05:07AM
(#34388255)
> then more computers if no issues were detected.
.. a job they should have left to the sysadmins in charge of those machines receiving said updates.
Re:Ubuntu 22.04 LTS servers and phased apt updates
by charcircuit on Sunday January 15, 2023 @06:30AM
(#34388637)
Why do you think pushing out broken updates to people and causing them to do extra work is a good thing? It's something that should happen as little as possible.
If the OS developers have the ability to save thousands of man hours of their users they should do so.
Re:Ubuntu 22.04 LTS servers and phased apt updates
by SahAssar on Sunday January 15, 2023 @07:23AM
(#34388876)
Ubuntu does a lot of things in both server and desktop that might only make sense on desktop (if even there).
Re:Ubuntu 22.04 LTS servers and phased apt updates
by ekianjo on Sunday January 15, 2023 @05:12AM
(#34388276)
You do have a way of avoiding it as mentioned in the link by setting an identical machine id string
Re:Ubuntu 22.04 LTS servers and phased apt updates
by AshamedCaptain on Sunday January 15, 2023 @05:35AM
(#34388402)
And then after reusing /etc/machine-id everywhere you spend the day after that debugging miscellaneous systemd issues.
Re:Ubuntu 22.04 LTS servers and phased apt updates
by drothlis on Sunday January 15, 2023 @05:48AM
(#34388466)
In the article they don't change /etc/machine-id, but APT::Machine-ID in apt.conf.
Re:Ubuntu 22.04 LTS servers and phased apt updates
by brnt on Sunday January 15, 2023 @06:04AM
(#34388523)
Who runs a fleet without their own apt cache server?
Re:Ubuntu 22.04 LTS servers and phased apt updates
by Symbiote on Sunday January 15, 2023 @06:39AM
(#34388676)
* * *
Re:Ubuntu 22.04 LTS servers and phased apt updates
by brnt on Sunday January 15, 2023 @06:58AM
(#34388757)
That should isolate you from this issue, shouldn't it?
Re:Ubuntu 22.04 LTS servers and phased apt updates
by soneil on Sunday January 15, 2023 @11:56AM
(#34390857)
I don't believe mirrors and caches affect this behaviour.
How this works is that the package index contains a stanza Phased-Update-Percentage: giving a number between 0 and 100. Then your client picks a number in the same range, and accepts an update if the repository's value is higher than the client's value.
Whether the fixed value comes from your mirror or Ubuntu's, makes no odds - You still have a fixed value on the server and a variable value on the client, so the outcome is still variable. Caching the index, or mirroring it without regenerating it, still leaves this decision to the end client.
Re:Ubuntu 22.04 LTS servers and phased apt updates
by philjohn on Sunday January 15, 2023 @06:36AM
(#34388662)
There is a way to avoid it, disable phased updates as detailed here: https://news.ycombinator.com/item?id=34388575
A practical problem with these phased updates is that you may end up with different versions of some software on your fleet of (until now) identical servers and you have no way of avoiding it.