Merge ~ines-almeida/launchpad-buildd:update-deployment-documentation into launchpad-buildd:master

[Ines Almeida]

Update deployment documentation

Remove note that is not valid; Add mention of which series to run `copy-package` command for qastaging

[Simone Pelosi (pelpsi)]

LGTM!

review: Approve

[Otto Co-Pilot (otto-copilot)]

Running landing tests failed.
https://jenkins.ols.ps5.canonical.com/job/launchpad-buildd/274/

diff --git a/docs/how-to/deployment.rst b/docs/how-to/deployment.rst
index aad49eb..896fcba 100644
--- a/docs/how-to/deployment.rst
+++ b/docs/how-to/deployment.rst
@@ -36,7 +36,10 @@ Testing on qastaging
    --to=ppa:launchpad/ubuntu/buildd-staging -b launchpad-buildd``
    (from ``ubuntu-archive-tools``) to copy the current version of launchpad-buildd
    to the deployment PPA (``jammy`` here refers to the series being used on
-   qastaging builder instances).
+   the builder instances).
+
+   For example, in qastaging, we have builders in ``focal`` and in ``jammy``,
+   so you should run the command for both series.
 
 #. `Wait for PPA publishing to complete
    <https://launchpad.net/~launchpad/+archive/ubuntu/buildd-staging/+packages>`__.
@@ -47,17 +50,6 @@ Testing on qastaging
    show "Synchronising images"; once this says "Sync completed", images have
    been rebuilt.
 
-   Note that if ``mojo run -m manifest-rebuild-images`` fails, run ``mojo run``
-   instead.
-
-   .. note::
-      Some glance-simplestreams-sync units may be in an unknown state:
-      as a consequence, the images that we have in OpenStack for the 
-      affected units are not updated. This will cause an `error
-      <https://pastebin.canonical.com/p/ChfGwsQNGJ/>`_ 
-      when you try to rebuild images blocking the execution of the script.
-      This doesn't happen using `mojo run`.
-
 #. Builders will get the new image after they finish their next build (or
    are disabled) and go through being reset.  Since qastaging's build farm
    is typically mostly idle, you can use ``manage-builders -l qastaging