Advise user to disable version pinning after upgrade
Now that the ovn-chassis charm has the ``enable-version-pinning`` configuration option, which has been backported to the 22.03 charm, advise user to disable version pinning after completing the 20.03 to 22.03 upgrade. pmatulis: * Clarify wording around versions and upgrades. * Add a table of contents due to the length of this page. Related-Bug: #2030944 Closes-Bug: #2042478 Signed-off-by: Frode Nordahl <frode.nordahl@canonical.com> Change-Id: I4e081814a0df2e11aeb4f61775b549828fdeaf89
This commit is contained in:
parent
28e08ccdb1
commit
2099dfd654
|
@ -24,6 +24,11 @@ that can cause network disruption to all cloud VMs.
|
|||
It is recommended that the upgrade be tested in a staged environment prior
|
||||
to applying the steps to a production cloud.
|
||||
|
||||
.. contents:: Contents:
|
||||
:local:
|
||||
:depth: 4
|
||||
:backlinks: top
|
||||
|
||||
Prerequisites
|
||||
-------------
|
||||
|
||||
|
@ -311,6 +316,26 @@ change, restart OVN Metadata agents with:
|
|||
not re-register in the new database table and Neutron will not be able to
|
||||
detect these agents.
|
||||
|
||||
Disable version pinning
|
||||
.......................
|
||||
|
||||
The 22.03 version of the ovn-chassis charm defaults to enforcing version
|
||||
pinning. This was necessary to support the upgrade procedure you have just
|
||||
completed.
|
||||
|
||||
Once 22.03 is running, however, this default is undesirable as it may cause
|
||||
upgrade issues when minor updates to the OVN packages are released.
|
||||
|
||||
From OVN LTS version 22.03 and onwards, rolling chassis upgrades are supported
|
||||
when upgrading to minor versions as well as to any version within the next
|
||||
major OVN LTS version.
|
||||
|
||||
Therefore, to ensure smooth cluster operation, disable version pinning:
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
juju config ovn-chassis enable-version-pinning=false
|
||||
|
||||
Neutron
|
||||
^^^^^^^
|
||||
|
||||
|
|
Loading…
Reference in New Issue