** Attachment added: "messages.xz"
https://bugs.launchpad.net/maas/+bug/1427160/+attachment/4378128/+files/messages.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1427160
Title:
MAAS allocates
** Attachment added: "partman.xz"
https://bugs.launchpad.net/maas/+bug/1427160/+attachment/4378129/+files/partman.xz
** Changed in: partman-auto (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
IRC chat from the day we debugged this:
< cjwatson> It's clearly considering the atomic recipe ineligible for some
reason.
< cjwatson> Probably because it thinks that its computed minimum size is
greater than the free size.
< ivoks> how much memory do this machines have?
< ivoks> i suspect more
I see no immediate reason why things would fallback to the home recipe
like this, default indeed seems like it should be atomic anyway.
Furthermore, seeing as explicitly specifying atomic seems to fix it, I'm
not sure what to think of this bug report. Please provide
/var/log/installer/syslog and/or
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: partman-auto (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1427160
Title:
Uniqness of this machine is that it had a lot more RAM than disk.
partman-auto couldn't deploy 'atomic' recipe and went with next one,
which was 'home'. This can happen with regular d-i, without MAAS.
** Also affects: partman-auto (Ubuntu)
Importance: Undecided
Status: New
** Tags added
