Merge ~cjwatson/launchpad-buildd:self-service-rebuild-images into launchpad-buildd:master

Proposed by Colin Watson
Status: Merged
Approved by: Colin Watson
Approved revision: 8c3423b9830242c076c7cea411781e902725e72f
Merge reported by: Otto Co-Pilot
Merged at revision: not available
Proposed branch: ~cjwatson/launchpad-buildd:self-service-rebuild-images
Merge into: launchpad-buildd:master
Diff against target: 36 lines (+21/-4)
1 file modified
docs/how-to/deployment.rst (+21/-4)
Reviewer Review Type Date Requested Status
Jürgen Gmach Approve
Review via email: mp+427615@code.launchpad.net

Commit message

Describe waiting for image rebuilds in more detail

Description of the change

In https://code.launchpad.net/~cjwatson/launchpad-buildd/+git/launchpad-buildd/+merge/427478, Jürgen asked "How do you know the image building has finished?" We don't have a straightforward view of this, unfortunately, but here's some more detail.

To post a comment you must log in.
Revision history for this message
Jürgen Gmach (jugmac00) wrote :

thanks for clarifying

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1diff --git a/docs/how-to/deployment.rst b/docs/how-to/deployment.rst
2index 8e9d83e..6952c28 100644
3--- a/docs/how-to/deployment.rst
4+++ b/docs/how-to/deployment.rst
5@@ -85,10 +85,27 @@ Releasing to production
6 staging management environment (``stg-vbuilder@launchpad-bastion-ps5``)
7 to start rebuilding images.
8
9-#. Once image builds complete, builders will get the new image after they
10- finish their next build (or are disabled) and go through being reset.
11- `Build farm administrators
12+#. Once the new image is rebuilt, which normally takes on the order of 15-60
13+ minutes depending on the architecture, builders will get the new image
14+ after they finish their next build (or are disabled) and go through being
15+ reset. As a result, ``manage-builders -v`` should start showing the new
16+ version over time.
17+
18+#. Wait for the new version to appear for at least one builder in each
19+ region and architecture (other than ``riscv64``, which is managed
20+ separately). If this doesn't happen after 90 minutes, then ask IS for
21+ assistance in investigating; they can start by checking ``juju status``
22+ in ``prod-launchpad-vbuilders@is-bastion-ps5.internal``.
23+
24+#. Once the updated version is visible for at least one builder in each
25+ region and architecture (other than ``riscv64``), `build farm
26+ administrators
27 <https://launchpad.net/~launchpad-buildd-admins/+members>`_ can use
28- ``manage-builders --virt --idle --reset`` to reset idle builders.
29+ ``manage-builders --virt --idle --builder-version=<old-version> --reset``
30+ to reset idle builders, thereby causing builders that haven't taken any
31+ builds recently to catch up.
32+
33+#. Ask Colin Watson or William Grant to reflash ``riscv64`` builders to the
34+ new version (currently a separate manual process).
35
36 #. Close any bugs fixed by the new release.

Subscribers

People subscribed via source and target branches