maas-devel team mailing list archive

[Raphaël Badin <raphael.badin@xxxxxxxxxxxxx>]

On 07/14/2014 08:20 AM, Julian Edwards wrote:
> On Friday 11 Jul 2014 19:27:09 Andreas Hasenack wrote:
> > > I upgraded another MAAS 1.5.2 to this beta4 and here are my observations:
>
> Thank you for helping with the testing Andreas.
>
> > > - apparently one needs to import boot images again. Machines were just not
> > > booting correctly, getting iscsi errors, images not found, etc. I clicked
> > > on the import images button, waited for a while (had to use a network
> > > monitor to know something was going on) and eventually had the magic
> > > number
> > > for boot images available (129). Then booting worked again on my nodes.
>
> You should not have to re-import again, this is a bug [1] (one which I thought
> was fixed as this is a known problem).
>
> [1] https://bugs.launchpad.net/maas/+bug/1338690
>
> Raphael, you QAed this, did you get as far as booting nodes with the QA?

Both Blake and I QAed the fix for bug 1338690 and we made sure that the 
images are detected from an old import (QA steps were: install 1.5 > 
import images > upgrade > Wipe out the Image table > wait for the images 
scanner to run > Check that the images are imported).

We didn't get as far as booting nodes (that's something I've done before 
the fix for 1338690) but we should have because the fix in question 
introduced bug https://bugs.launchpad.net/maas/+bug/1341001 (Blake is 
working on it).

I think bug 1341001 is the reason why Andreas had to re-import the images.