[Labs-l] Precise image updated

[Tim Landscheidt]

Ryan Lane <rlane32 at gmail.com> wrote:

> I've updated the custom image we use for precise instances. Here's some
> info about the new image:

> 1. It updates the salt configuration that was used in the old image, making
> it easier for us to migrate to eqiad and makes instance creation more
> reliable.
> 2. It adds the ubuntu-standard package, which provides a number of packages
> missing from the old image.
> 3. It ensures a newly installed instance has a relatively small number of
> outdated packages.
> 4. It adds a firstboot script, which takes what was previously being done
> with a cloud-init script and moves it into the image. This will make it
> easier to allow direct access to the APIs in the future and also makes it
> easier for us to move to eqiad.

> If you run into any issues building images using the precise image, let me
> know.

When I create new instances in the Toolsbeta project (Pre-
cise image, small and xsmall, no configuration), after
building is complete:

| scfc@:~$ sudo puppetd -tv
| info: Creating a new SSL key for i-00000906.pmtpa.wmflabs
| info: Caching certificate for i-00000906.pmtpa.wmflabs
| err: Could not request certificate: The certificate retrieved from the master does not match the agent's private key.
| Certificate fingerprint: 92:68:EB:8A:2C:C4:68:61:3B:FD:F6:C8:9E:41:B2:00
| To fix this, remove the certificate from both the master and the agent and then start a puppet run, which will automatically regenerate a certficate.
| On the master:
|   puppet cert clean i-00000906.pmtpa.wmflabs
| On the agent:
|   rm -f /var/lib/puppet/ssl/certs/i-00000906.pmtpa.wmflabs.pem
|   puppet agent -t

| Exiting; failed to retrieve certificate and waitforcert is disabled
| scfc@:~$

The instance ID (906) remains the same, even though the ac-
tual ID of the instance is for example 9d0.  Is this re-
lated?

Tim