Both network "outages" could have been prevented by adding a note at the
end of the dist-upgrade output.
e.g. something like the following (monospace font required for the >"Attention" text):
_ _____ _____ _____ _ _ _____ ___ ___ _ _
/ \|_ _|_ _| ____| \ | |_ _|_ _/ _ \| \ | |
/ _ \ | | | | | _| | \| | | | | | | | | \| |
/ ___ \| | | | | |___| |\ | | | | | |_| | |\ |
/_/ \_\_| |_| |_____|_| \_| |_| |___\___/|_| \_|
Network interface name changed: please update config files before reboot.
On Tue, 4 Mar 2025 20:39:43 -0500, "Helmut K. C. Tessarek" <tessarek@evermeet.cx> wrote:
Both network "outages" could have been prevented by adding a note at the >end of the dist-upgrade output.
e.g. something like the following (monospace font required for the >"Attention" text):
_ _____ _____ _____ _ _ _____ ___ ___ _ _
/ \|_ _|_ _| ____| \ | |_ _|_ _/ _ \| \ | |
/ _ \ | | | | | _| | \| | | | | | | | | \| |
/ ___ \| | | | | |___| |\ | | | | | |_| | |\ |
/_/ \_\_| |_| |_____|_| \_| |_| |___\___/|_| \_|
Network interface name changed: please update config files before reboot.
Why would people who do not read the NEWS.Debian or the Release Notes
read that? And how would you solve the issue of people wanting more
and more of those attention banners?
On Wed, Mar 05, 2025 at 04:06:56PM +0100, Marc Haber wrote:
On Tue, 4 Mar 2025 20:39:43 -0500, "Helmut K. C. Tessarek"
<tessarek@evermeet.cx> wrote:
Both network "outages" could have been prevented by adding a note at the >> >end of the dist-upgrade output.Why would people who do not read the NEWS.Debian or the Release Notes
e.g. something like the following (monospace font required for the
"Attention" text):
_ _____ _____ _____ _ _ _____ ___ ___ _ _
/ \|_ _|_ _| ____| \ | |_ _|_ _/ _ \| \ | |
/ _ \ | | | | | _| | \| | | | | | | | | \| |
/ ___ \| | | | | |___| |\ | | | | | |_| | |\ |
/_/ \_\_| |_| |_____|_| \_| |_| |___\___/|_| \_|
Network interface name changed: please update config files before reboot. >>
read that? And how would you solve the issue of people wanting more
and more of those attention banners?
Presumably because it will be written directly to their terminal.
Noticing the one change among the umpteen more-or-less-major NEWS
entries that actually affects the ability of your system to safely
reboot with the same network configuration is not a trivial task, even
for reasonably experienced sysadmins.
On Wed, Mar 05, 2025 at 06:29:26PM +0100, Matthias Urlichs wrote:
Noticing the one change among the umpteen more-or-less-major NEWS
entries that actually affects the ability of your system to safely
reboot with the same network configuration is not a trivial task, even
for reasonably experienced sysadmins.
It is also a challenge for a package maintainer to judge WHEN to drop
a higher priority NEWS entry.
I think that our release notes recommend one or another way for console access for upgrades for exactly this reason.
On 05.03.25 17:16, Bjørn Mork wrote:
apt install apt-listchanges
To be fair, apt-listchanges lists a whole lot of changes, esp. when
you do a dist-upgrade.
Noticing the one change among the umpteen more-or-less-major NEWS
entries that actually affects the ability of your system to safely
reboot with the same network configuration is not a trivial task, even
for reasonably experienced sysadmins.
I doubt there are more than one or at max two items that would break
network connectivity.
This is my first mail in a Debian mailing list and I hope I've chosen the correct one. There are way too many lists thus please direct me to the correct one, in case I messed up.
In the last few days I ran into a serious issue when upgrading to newer releases on 3 headless servers: the network connection went dead.
In the first situation the interface name changed from eth0 to end0 and
after the reboot my adapter got a link-local address.
In the second situation dhcpcd was replaced by Network Manager and once
again the network was dead.
Both network "outages" could have been prevented by adding a note at the end of the dist-upgrade output.
On 05.03.25 21:35, Marc Haber wrote:
And which of the millions of changes would that be that would break
YOUR system?
The number of changes that can adversely impact your ability to boot
*or* your network connectivity (but which won't fail the upgrade!) can
safely be assumed to be smaller than five or so.
Both network "outages" could have been prevented by adding a note at the end of the dist-upgrade output.
On the other
hand, it's not always possible to have a test bed for every single setup.
P.S.: This failure mode isn't even documented in the release notes.
On Tue, Mar 04, 2025 at 08:39:43PM -0500, Helmut K. C. Tessarek wrote:
Both network "outages" could have been prevented by adding a note at the end
of the dist-upgrade output.
they could also have been prevented by reading the release notes and following
their advice.
Which entry in which release notes will warn that this time
(presumably - was this an upgrade to unstable K.C. or to bookworm, or >something else?) the (pretty old now) eth0 -> 'annoying, unmemorable,
but ordered and unique', renaming will/might actually break your
config?
Which entry in which release notes will warn that this time
(presumably - was this an upgrade to unstable K.C. or to bookworm, or something else?) the (pretty old now) eth0 -> 'annoying, unmemorable,
but ordered and unique', renaming will/might actually break your
config?
On Tue, 4 Mar 2025 20:39:43 -0500, "Helmut K. C. Tessarek"
<tessarek@evermeet.cx> wrote:
Network interface name changed: please update config files before reboot.
P.S.: This failure mode isn't even documented in the release notes.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 147:33:22 |
| Calls: | 10,383 |
| Calls today: | 8 |
| Files: | 14,054 |
| D/L today: |
2 files (1,861K bytes) |
| Messages: | 6,417,731 |