Adding LXD Pod with pre-composed resources errors out

Bug #1874538 reported by Newell Jensen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Newell Jensen

Bug Description

When trying to add a LXD Pod from the maas cli I get the below traceback. This has to do with the face that I had a pre-composed VM in LXD.

==> /var/log/maas/rackd.log <==
   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1386, in _inlineCallbacks
     result = g.send(result)
   File "/usr/lib/python3/dist-packages/provisioningserver/drivers/pod/lxd.py", line 326, in discover
     cpu_speed=discovered_pod.cpu_speed,
   File "/usr/lib/python3/dist-packages/provisioningserver/drivers/pod/lxd.py", line 182, in get_discovered_machine
     storage_pool=pool,
   File "<attrs generated init 86327313f484cbc7ef217a50d76b6637e4e4ccc6>", line 4, in __init__
     self.size = __attr_converter_size(size)
 builtins.ValueError: invalid literal for int() with base 10: '20GB'

Related branches

Alberto Donato (ack)
Changed in maas:
milestone: 2.8.0b2 → 2.8.0rc1
Changed in maas:
status: In Progress → Fix Committed
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.

Other bug subscribers

Remote bug watches

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