From 4f49b4a1a96ccafdc6c7105b596ee6a67e9b7487 Mon Sep 17 00:00:00 2001 From: Dimple Kuriakose Date: Sat, 3 Oct 2026 19:41:13 +0530 Subject: [PATCH] fix(GCP): Remove the specific Focal to Jammy upgrade guide, now that we have a generic LTS upgrade guide --- docs/google/google-how-to/gce/index.rst | 2 - .../gce/upgrade-from-focal-to-jammy.rst | 97 ------------------- docs/google/google-how-to/index.rst | 1 - docs/google/index.rst | 2 +- 4 files changed, 1 insertion(+), 101 deletions(-) delete mode 100644 docs/google/google-how-to/gce/upgrade-from-focal-to-jammy.rst diff --git a/docs/google/google-how-to/gce/index.rst b/docs/google/google-how-to/gce/index.rst index e83c153e..8533fb2c 100644 --- a/docs/google/google-how-to/gce/index.rst +++ b/docs/google/google-how-to/gce/index.rst @@ -25,7 +25,6 @@ Performing upgrades: * :ref:`Change license between LTS and Pro ` * :ref:`Enable Pro features ` -* :ref:`Upgrade from Focal to Jammy ` * :ref:`Upgrade Ubuntu LTS release ` Administrative operations: @@ -43,7 +42,6 @@ Administrative operations: Create customized docker containers Change license between LTS and Pro Enable Pro features - Upgrade from Focal to Jammy Upgrade Ubuntu LTS release Set hostname Use 64K page kernel on ARM64 diff --git a/docs/google/google-how-to/gce/upgrade-from-focal-to-jammy.rst b/docs/google/google-how-to/gce/upgrade-from-focal-to-jammy.rst deleted file mode 100644 index 49a767ae..00000000 --- a/docs/google/google-how-to/gce/upgrade-from-focal-to-jammy.rst +++ /dev/null @@ -1,97 +0,0 @@ -.. meta:: - :description: Learn how to upgrade Ubuntu from 20.04 LTS (Focal) to 22.04 LTS (Jammy) on GCE. Includes detailed steps for performing an in-place upgrade using do-release-upgrade. - -.. _upgrade-from-focal-to-jammy: - -Upgrade from Focal to Jammy on GCE -================================== - -General Advice ---------------- - -Once you have decided to upgrade your system, the next question is how? There are two options depending on whether your system is setup/deployed with automation or whether it requires manual configuration. - -For fully automated system deployments it is recommended to redeploy with new Jammy instances instead of upgrading from Focal. - -For systems that cannot be easily created or destroyed and require manual configuration, running `do-release-upgrade `_ is a good option. However this option requires some :ref:`manual intervention ` as explained below. - -.. _manual intervention gce: - -Manual intervention steps -------------------------- - -While upgrading from Focal to Jammy, manual decision making will be needed for the following options that are presented. - -Additional SSH daemon -~~~~~~~~~~~~~~~~~~~~~ - -When upgrading in a session over SSH there is an inherent risk of losing access if something goes wrong with the SSH daemon. To mitigate this risk an additional SSH daemon is started on a different port as a backup. - -The prompt notifies you that an additional SSH daemon will be started and you can either continue or cancel the upgrade. - -.. image:: upgrade-from-focal-to-jammy-images/0_additional_ssh_daemon.png - :align: center - - -Optional firewall rules for additional SSH daemon -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -If you are using a firewall there is a chance that the port used by the backup SSHD is not open. Opening this port is not done automatically since it could be security risk. An optional command to open the port is provided and you are prompted to press enter to continue. - -.. image:: upgrade-from-focal-to-jammy-images/1_firewall_for_additional_ssh.png - :align: center - - -Start upgrade -~~~~~~~~~~~~~ -A final prompt is provided before starting the upgrade. It gives information about the number of changes and the estimated time to complete because once started, the upgrade process cannot be canceled. At this stage you can continue, cancel or see additional details. - -.. image:: upgrade-from-focal-to-jammy-images/2_start_upgrade.png - :align: left - - -Restart services automatically -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -During the upgrade of certain libraries, some services have to be restarted. You have the option of allowing the services to be restarted automatically during the upgrade. If you select 'no' here, you'll be asked about the services that you want to restart after each library upgrade. - -.. image:: upgrade-from-focal-to-jammy-images/3_restart_services.png - :align: center - - -SSHD configuration modified -~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Canonical makes changes to ``/etc/ssh/sshd_config`` for GCP images. As a result, during upgrade you'll see a prompt notifying you about the availability of a newer version of the sshd_config file. You'll be asked if you want to keep the existing modified version, use the default one from the new upgrade or take some other action. - -.. image:: upgrade-from-focal-to-jammy-images/4_sshd_modified_config.png - :align: center - - -Chrony configuration modified -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Due to a possible bug in ``ucf``, even if there are no changes in ``/etc/chrony/chrony.conf`` you'll be shown a prompt asking whether you want to keep the current version, use the default one from the new upgrade, or take some other action. - -.. image:: upgrade-from-focal-to-jammy-images/5_chrony_modified_config.png - :align: center - - -Remove obsolete packages -~~~~~~~~~~~~~~~~~~~~~~~~ - -An obsolete package is a package which is no longer available in any of the sources for apt. Usually it is safe and recommended to remove obsolete packages. But before doing so you'll be asked if you wish to remove them and you'll have the option to select from yes, no and more details. - -.. image:: upgrade-from-focal-to-jammy-images/6_remove_obsolete.png - :align: center - - -Restart to finish upgrade -~~~~~~~~~~~~~~~~~~~~~~~~~ - -Finally, a restart will be necessary for some parts of the upgrade to be applied. If you select no, you can use ``/var/run/reboot-required.pkgs`` to check for the packages that need a reboot. - -.. image:: upgrade-from-focal-to-jammy-images/7_finish_upgrade.png - :align: center - - diff --git a/docs/google/google-how-to/index.rst b/docs/google/google-how-to/index.rst index 34e3f682..049bf8ba 100644 --- a/docs/google/google-how-to/index.rst +++ b/docs/google/google-how-to/index.rst @@ -20,7 +20,6 @@ While using Ubuntu on GCP, you'll need to perform tasks such as finding the righ * :ref:`Create customized docker containers ` * :ref:`Change license between LTS and Pro ` * :ref:`Enable Pro features ` -* :ref:`Upgrade from Focal to Jammy ` * :ref:`Upgrade Ubuntu LTS release ` * :ref:`Set hostname ` * :ref:`Use 64K page kernel on ARM64 instances ` diff --git a/docs/google/index.rst b/docs/google/index.rst index 9e89a36c..05eb4c5b 100644 --- a/docs/google/index.rst +++ b/docs/google/index.rst @@ -34,7 +34,7 @@ In this documentation - :ref:`Find images ` • :ref:`Create instances ` • :ref:`Launch a desktop ` • :ref:`Use 64K page kernel on ARM64 instances ` * - **Upgrades and maintenance** - - :ref:`Switch between LTS and Pro ` • :ref:`Enable Ubuntu Pro features ` • :ref:`Upgrade from Focal to Jammy ` • :ref:`Upgrade Ubuntu LTS release ` + - :ref:`Switch between LTS and Pro ` • :ref:`Enable Ubuntu Pro features ` • :ref:`Upgrade Ubuntu LTS release ` * - **Creating golden images** - :ref:`Build a Pro golden image `