Hi, Please find attached my proposal for the release notes to cover bug #990069.
Disclaimer: I (or somebody else) still have (has) to verify that the procedure works as intended. One can clearly start a very limited upgrade with only openssh-server, but what needs checking is that: a) ssh login works after the partial upgrade b) with openssh-server upgraded, the downtime for accepting new connections is greatly reduced. Paul
From 6f71007b1c0bf282dc3a9a17c5b958b1489e9ace Mon Sep 17 00:00:00 2001
From: Paul Gevers <elb...@debian.org>
Date: Fri, 6 Aug 2021 17:50:07 +0200
Subject: [PATCH] issues.dbk: no new ssh connections possible during upgrade
Bug: #990069
---
en/issues.dbk | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/en/issues.dbk b/en/issues.dbk
index d3386a9b..9b0687a2 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -539,6 +539,21 @@ data = ${lookup{$local_part}lsearch{/some/path/$domain_data/aliases}}
</para>
</section>
+ <section id="ssh-not-available">
+ <title>No new ssh connections possible during upgrade</title>
+ <para>
+ Due to unfortunate circumstances it's not possible to establish
+ new <command>ssh</command> connections for a bigger part of the
+ upgrade than during previous release upgrades. As usual,
+ existing connections should continue to work, but if the upgrade
+ is done over <command>ssh</command> and the
+ <command>ssh</command> connection is not trusted to last for the
+ full upgrade period, it's adviced to upgrade <systemitem
+ role="package">openssh-server</systemitem> before upgrading the
+ full system.
+ </para>
+ </section>
+
<section id="before-first-reboot">
<title>Things to do post upgrade before rebooting</title>
<!-- If there is nothing to do -->
--
2.30.2
OpenPGP_signature
Description: OpenPGP digital signature
