MAAS

default KVM pod RAM (1GB) is not enough to commission

Bug #1877126 reported by Junien F
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Lee Trager
MAAS 2.8.0rc1

Bug Description

Hi,

Using MAAS snap 2.7.0-8235-g.fea3a1678, Ubuntu 20.04.

If I compose a KVM machine without filling any field, I get a pod with 1GB RAM. This is apparently not enough to commission it :

[ 61.317272] Out of memory: Killed process 1681 (apt-check) total-vm:68640kB, anon-rss:44860kB, file-rss:2956kB, shmem-rss:0kB, UID:0 pgtables:176kB oom_score_adj:0

I really think we should be able to install an Ubuntu system which has 1G RAM ? I wonder if this is something that's tracked by Ubuntu Foundations.

Else the default needs to be increased :)

Thanks !

Related branches

~ltrager/maas:lp1877126
Björn Tillenius: Approve
MAAS Lander: Approve
Diff: 203 lines (+61/-20)
3 files modified
src/maasserver/clusterrpc/driver_parameters.py (+15/-1)
src/maasserver/forms/pods.py (+20/-5)
src/maasserver/forms/tests/test_pods.py (+26/-14)
Revision history for this message
Junien F (axino) wrote :

Also displaying the default in the "empty" fields would be nice, so that you know what you're getting if you press "Compose machine"

Revision history for this message
Dougal Matthews (d0ugal) wrote :

Granted, I have been using 2.8.0~beta3-8449-g.bf5c42a71, but I am able to commission a machine with the defaults. I'll try on 2.7

Revision history for this message
Lee Trager (ltrager) wrote :

I can commission Bionic with 1GB of RAM, Focal fails. The Focal image is much bigger, 179M for Bionic AMD64 vs 346M for Focal AMD64. In Focal LXD is now isntalled as a Snap which requires more RAM. When I commissioned using Focal on a 4GB VM at idle the system was using 1244M of RAM, Bionic uses 677M of RAM at idle on the same VM.

AFAIK no one is tracking how much RAM Ubuntu images use. Netbooting does requires additional RAM as the entire OS image, kernel, and initrd must be stored in memory.

I agree MAAS should work with VMs that have 1GB of RAM. I'm not opposed to changing the default memory size but we should still allow 1GB for older versions of Ubuntu.

Revision history for this message
Björn Tillenius (bjornt) wrote :

As Lee said, there's not much MAAS can do to make Focal work with 1Gb of RAM. It's something for Foundations to look at.

I think we should simply change the default to 2Gb. That's only a default, the user is free to change it to whatever he wants, but it makes sense that the default works in most condition.

We should bring this up with Ubuntu Foundations before we switch to Focal for the default commissioning environment.

Changed in maas:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.8.0b4
Adam Collard (adam-collard)
tags: added: ui
Revision history for this message
Caleb Ellis (caleb-ellis) wrote :

It seems that there isn't so much a "default" RAM as there is a minimum, where if nothing is sent then the minimum is assumed.

If you were to explicitly set a default in the backend, and we wanted to show it in the UI, I would ask that that number be exposed somewhere over the websocket. Just so then we only have to make the change once.

Alberto Donato (ack)
Changed in maas:
milestone: 2.8.0b4 → 2.8.0rc1
Revision history for this message
Adam Collard (adam-collard) wrote :

Let's expose the default over the websocket (if it's not already there) and bump to 2G

Changed in maas:
assignee: nobody → Lee Trager (ltrager)
Revision history for this message
Lee Trager (ltrager) wrote :

The related branch ups the default memory amount to 2048M. The websocket now include the default core and memory amount in the BMC listing for Pod types.

Changed in maas:
status: Triaged → In Progress
MAAS Lander (maas-lander)
Changed in maas:
status: In Progress → Fix Committed
Revision history for this message
Lee Trager (ltrager) wrote :

The backend has landed which ups the default KVM pod memory to 2GB. The web socket now includes the default cores, memory, and disk storage amounts. I've set this bug back to new so the design team can incorporate the defaults into the UI.

Changed in maas:
status: Fix Committed → New
Lee Trager (ltrager)
Changed in maas:
status: New → Fix Committed
Revision history for this message
Lee Trager (ltrager) wrote :

I decided to just close this and track the UI part separately in LP:1879772.

tags: removed: ui
Alberto Donato (ack)
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.