Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.devel > #116222

Re: Improvement of headless server upgrades

From Fabio Fantoni <fantonifabio@tiscali.it>
Newsgroups linux.debian.devel
Subject Re: Improvement of headless server upgrades
Date 2025-03-06 11:30 +0100
Message-ID <KngEh-40Ni-3@gated-at.bofh.it> (permalink)
References <KmMPT-3GDg-1@gated-at.bofh.it> <Knf5v-3ZBD-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Il 06/03/2025 09:43, Holger Levsen ha scritto:
> 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.
>
> that would also have prevented this wonderful bikeshedding thread.
>
> sorry to state the obvious.
>
>
I think the things to do can be summed up as follows: read release note 
of new major version and NEWS entries

If you are upgrading important or critical systems try also:

- test before in a testing system, or vm. or even just start from a less 
critical one

- try to have additional access in case of unforeseen events (there are 
not only the network ones mentioned in this discussion that can prevent 
the boot but also other undocumented and/or specific ones to the system 
or to a part of it). I mean for example an access from the host in case 
of vm or an ipmi system in case of physical server.

- if you don't have much time to read the whole release note read at 
least the "Upgrade specific items" part, for example for buster there is 
"5.1.6. Migrating from legacy network interface names".

- if you don't have time to read NEWS every update do it at least for 
the first time so you can see all the common ones on the basic packages, 
for example however it can be useful to have a quick look at each update 
and read those of specific programs to be aware of important or 
essential changes and save time rather than having problems later, 
perhaps not noticing the problems immediately or not being able to find 
the cause immediately


Regarding possible improvements I think the only thing that can be added 
is a check to the upgrade operations and if it is detected that you are 
upgrading to packages of the next major version add a simple initial 
warning (but not a big "image" as suggested in topic start) in which it 
is recommended to read the release notes, especially the "Upgrade 
specific items" part, and the NEWS of the packages.

Back to linux.debian.devel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Improvement of headless server upgrades "Helmut K. C. Tessarek" <tessarek@evermeet.cx> - 2025-03-05 03:40 +0100
  Re: Improvement of headless server upgrades Fabio Fantoni <fantonifabio@tiscali.it> - 2025-03-05 10:30 +0100
  Re: Improvement of headless server upgrades Marc Haber <mh+debian-devel@zugschlus.de> - 2025-03-05 16:10 +0100
    Re: Improvement of headless server upgrades Michael Banck <mbanck@debian.org> - 2025-03-05 16:20 +0100
      Re: Improvement of headless server upgrades Bjørn Mork <bjorn@mork.no> - 2025-03-05 17:50 +0100
        Re: Improvement of headless server upgrades Matthias Urlichs <matthias@urlichs.de> - 2025-03-05 19:30 +0100
          Re: Improvement of headless server upgrades Marc Haber <mh+debian-devel@zugschlus.de> - 2025-03-05 20:40 +0100
            Re: Improvement of headless server upgrades Soren Stoutner <soren@debian.org> - 2025-03-05 21:00 +0100
          Re: Improvement of headless server upgrades "Helmut K. C. Tessarek" <tessarek@evermeet.cx> - 2025-03-05 20:40 +0100
          Re: Improvement of headless server upgrades Bjørn Mork <bjorn@mork.no> - 2025-03-05 21:10 +0100
            Re: Improvement of headless server upgrades Marc Haber <mh+debian-devel@zugschlus.de> - 2025-03-05 21:40 +0100
              Re: Improvement of headless server upgrades Matthias Urlichs <matthias@urlichs.de> - 2025-03-05 22:30 +0100
                Re: Improvement of headless server upgrades Marc Haber <mh+debian-devel@zugschlus.de> - 2025-03-06 09:00 +0100
            Re: Improvement of headless server upgrades "Helmut K. C. Tessarek" <tessarek@evermeet.cx> - 2025-03-05 21:40 +0100
      Re: Improvement of headless server upgrades "Helmut K. C. Tessarek" <tessarek@evermeet.cx> - 2025-03-05 20:40 +0100
        Re: Improvement of headless server upgrades Marc Haber <mh+debian-devel@zugschlus.de> - 2025-03-06 10:10 +0100
    Re: Improvement of headless server upgrades Marc Haber <mh+debian-devel@zugschlus.de> - 2025-03-06 15:50 +0100
    Re: Improvement of headless server upgrades Richard Lewis <richard.lewis.debian@googlemail.com> - 2025-03-07 01:50 +0100
  Re: Improvement of headless server upgrades Helmut Grohne <helmut@subdivi.de> - 2025-03-06 06:50 +0100
    Re: Improvement of headless server upgrades "Helmut K. C. Tessarek" <tessarek@evermeet.cx> - 2025-03-07 00:10 +0100
  Re: Improvement of headless server upgrades Holger Levsen <holger@layer-acht.org> - 2025-03-06 09:50 +0100
    Re: Improvement of headless server upgrades Fabio Fantoni <fantonifabio@tiscali.it> - 2025-03-06 11:30 +0100
    Re: Improvement of headless server upgrades Wookey <wookey@wookware.org> - 2025-03-06 15:20 +0100
      Re: Improvement of headless server upgrades Andrey Rakhmatullin <wrar@debian.org> - 2025-03-06 17:40 +0100
      Re: Improvement of headless server upgrades Bjørn Mork <bjorn@mork.no> - 2025-03-06 18:00 +0100
      Re: Improvement of headless server upgrades "Helmut K. C. Tessarek" <tessarek@evermeet.cx> - 2025-03-07 00:00 +0100
        Re: Improvement of headless server upgrades "Helmut K. C. Tessarek" <tessarek@evermeet.cx> - 2025-03-07 00:20 +0100

csiph-web