maas-builds team mailing list archive

[Diogo Matsubara <diogo.matsubara@xxxxxxxxxxxxx>]

On Thu, Feb 27, 2014 at 7:09 AM, Raphaël Badin
<raphael.badin@xxxxxxxxxxxxx>wrote:

> Meanwhile, I'm putting up a branch to make
>> get_default_arch_image_in_nodegroup() prefer i386 like that comment says.
>>
>
> I just got a successful test run using  MAAS 1.5+bzr1977+2032+245~ppa0~ubuntu14.04.1
> (a package that includes Jeroen's fix) (http://d-jenkins.ubuntu-ci:
> 8080/view/MAAS/job/maas-test/70/).
>
> I ssh'ed into the machine while the test was running and this is the list
> of the boot images: http://paste.ubuntu.com/7004164/. As you can see, no
> amd64/generic-trusty-commissioning image for some reason.  This explains
> the failure we've seen: instead of the amd64 images, the arm image was
> given to the nodes.
>
> Two questions remain:
> - Why is the amd64/generic-trusty-commissioning image not imported?
> - Why rebooting the nodes did seem to fix the problem yesterday?
>

Could this be a timing issue? Yesterday when I was trying to get some nodes
to enlist, I had to reboot the nodes a few times until they actually
grabbed the amd64 image.

I just tested with 1.5+bzr1977+2032+245~ppa0~ubuntu14.04.1 (
http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/trusty-adt-maas-manual/64/console)
and got a similar behavior you described in maas-test run #70.

Initially there wasn't any amd64/generic-trusty-commissioning image, but
after awhile it was there: http://pastebin.ubuntu.com/7004965/


> Cheers,
>
> R.
>
> --
Diogo M. Matsubara