Image testing fails after introduction of 'activities'

[Henrik Nilsen Omma]

After introducing the concept of activities the testing of images has broken.

Needs fixing urgently for the testing running up to the hardy point release.

[Marc Tardif (cr3)]

With the introduction of activities, requests to test images are initiated from the hardware certification website rather than from each satellite server. So, the probing of the image sites such as cdimage.u.c and releases.u.c is performed centrally and then corresponding activities can be enqueued for each satellite server. For example, upon probing a new milestone, a request could be enqueued to test all systems. As another example, upon probing a daily current image, a request could simply be enqueued for a single machine or one of each machine category.

In order to support this new concept, the satellite server should now run a derivation of the checkbox-compatibility project in order to exchange messages with the hardware certification website using a streamlined protocol. Furthermore, the code base now becomes more streamlined by using checkbox derivations instead of yet another design.

[Marc Tardif (cr3)]

The current status is that the following actions are performed by the satellite servers when an image is requested for testing:

1. Image is downloaded (rsync) for each satellite server.
2. If that succeeds, the systems for each satellite are prepared for
   install.

The only action missing is:

3. If the preparation succeeds, the systems should be rebooted.

The code for this last action is already there, so it just a question of debugging.