*** This bug is a duplicate of bug 1309593 ***
https://bugs.launchpad.net/bugs/1309593
** This bug is no longer a duplicate of bug 1311151
MAAS imports Trusty's 'rc' images by default.
** This bug has been marked a duplicate of bug 1309593
No way to specify which image should be used wh
*** This bug is a duplicate of bug 1311151 ***
https://bugs.launchpad.net/bugs/1311151
Hi Jeff, thanks for the detailed bug report, I'm duping this against bug
1311151 since this seems to be the main issue and how you workarounded
the problem. Given the other symptoms you describe this is poss
So it would seem to confirm that MAAS is choosing the older 20140410
images over the 20140416.1 images when installing.
This is my bootresources.yaml: (The only changes I made were commenting
out older versions I didn't want to pull down)
ubuntu@critical-maas:/var/lib/maas/boot-resources$ cat
/e
I went through and deleted the rc directory from *current, and also
deleted the individual images themselves (had to compare inode numbers
in rc/ to the images in cache and deleted the images individually by
inode.
Then I did an install and it installed the correct image by default:
ubuntu@superm
