... | ... | @@ -164,6 +164,12 @@ to 3.0.1-2 in Debian 11 "bullseye". There's a backport of 3.x in |
|
|
*bullseye* nodes without first having to upgrade all nodes in the
|
|
|
cluster to bullseye.
|
|
|
|
|
|
Update: it might be *mandatory* to *first* upgrade to
|
|
|
`bullseye-backports`, then purge the old packages, before upgrading to
|
|
|
bullseye, see [bug 993559][].
|
|
|
|
|
|
[bug 993559]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993559
|
|
|
|
|
|
### Release notes
|
|
|
|
|
|
We upgrade from 2.15 to 3.0.1, the [3.0.1 NEWS file](https://github.com/ganeti/ganeti/blob/v3.0.1/NEWS) has the
|
... | ... | @@ -186,8 +192,9 @@ relevant release notes (including 2.16 changes). Notable changes: |
|
|
|
|
|
### Procedure
|
|
|
|
|
|
This procedure should (ideally) be performed *before* the upgrade to
|
|
|
bullseye, but can also be performed after:
|
|
|
This procedure ~~should (ideally)~~ MUST (see [bug 993559][]) be
|
|
|
performed *before* the upgrade to bullseye, but can also be performed
|
|
|
after:
|
|
|
|
|
|
1. on all nodes, upgrade Ganeti to backports (obviously only
|
|
|
necessary on buster):
|
... | ... | @@ -349,6 +356,8 @@ See also the official list of [known issues](https://www.debian.org/releases/bul |
|
|
|
|
|
## Pending
|
|
|
|
|
|
* Ganeti packages fail to upgrade (see above and [bug 993559][])
|
|
|
|
|
|
* (from buster:) upgrading restarts openvswitch will mean all guests lose network
|
|
|
|
|
|
* (from buster:) Puppet might try to downgrade the `sources.list`
|
... | ... | |