MAAS

  1. Series 2.4
  2. Bug #1772099
  3. Comment #0

Comment 0 for bug 1772099

Revision history for this message
Michael Iatrou (michael.iatrou) wrote : Cannot overcommit storage for KVM pods, silent failure

This is a regression issue for:
maas 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1
maas-cli 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1
maas-common 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1
maas-dhcp 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1
maas-dns 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1
maas-proxy 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1
maas-rack-controller 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1
maas-region-api 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1
maas-region-controller 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1
python3-django-maas 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1
python3-maas-client 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1
python3-maas-provisioningserver 2.3.3-6498-ge4db91d-0ubuntu1~16.04.1

Composing a new KVM pod does not allow to overcommit local storage.
The action fails silently on the UI, and in the logs it reports:

==> /var/log/maas/regiond.log <==
2018-05-18 14:10:35 twisted.internet.defer: [critical] Unhandled error in Deferred:
2018-05-18 14:10:35 twisted.internet.defer: [critical]

Traceback (most recent call last):
Failure: provisioningserver.rpc.exceptions.PodInvalidResources: not enough space for disk 1.