launchpad-reviewers team mailing list archive

[Simone Pelosi <mp+461052@xxxxxxxxxxxxxxxxxx>]

Diff comments:

> diff --git a/docs/how-to/deployment.rst b/docs/how-to/deployment.rst
> index 7365bee..fbe4b22 100644
> --- a/docs/how-to/deployment.rst
> +++ b/docs/how-to/deployment.rst
> @@ -42,11 +42,14 @@ Testing on qastaging
>     <https://launchpad.net/~launchpad/+archive/ubuntu/buildd-staging/+packages>`__.
>  
>  #. Run ``mojo run -m manifest-rebuild-images`` in the management environment
> -   (``stg-vbuilder@launchpad-bastion-ps5``) to start rebuilding images.
> +   (``stg-vbuilder-qastaging@launchpad-bastion-ps5``) to start rebuilding images.
>     After a minute or so, ``juju status glance-simplestreams-sync-\*`` will
>     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.

Because it may happen that some glance-simplestreams-sync unit is in unknown state: thus means, from what I understood, that the images that we have in OpenStack for the affected unit are not updated. This will cause an error when you try to rebuild images: https://pastebin.canonical.com/p/ChfGwsQNGJ/ blocking the execution of the script.

This doesn't happen if you use `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


-- 
https://code.launchpad.net/~pelpsi/launchpad-buildd/+git/launchpad-buildd/+merge/461052
Your team Launchpad code reviewers is requested to review the proposed merge of ~pelpsi/launchpad-buildd:qastaging-documentation-improvement into launchpad-buildd:master.