Adding 20.04 images to MAAS causes UI tracebacks for TypeError: '<' not supported between instances of 'NoneType' and 'str'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Triaged
|
High
|
Unassigned |
Bug Description
This is seen on 2.6 installs:
MAAS version: 2.6.1 (7832-g17912cdc
MAAS version: 2.6.0~beta4 (7743-g27b04aaf
Two different MAAS servers with 2.6ish versions of MAAS.
I noticed today that 20.04 images are available for syncing, so I selected that on both maas servers and synced.
Once the images were downloaded, MAAS started throwing tracebacks in regiond.log and the UI now does not work.
On the UI, I get this:
Error occurredReload
'<' not supported between instances of 'NoneType' and 'str'
and in regiond.log I get this:
2019-11-05 16:33:54 maasserver.
Traceback (most recent call last):
File "/usr/lib/
File "/usr/lib/
return target()
File "/usr/lib/
task()
File "/usr/lib/
task()
--- <exception caught here> ---
File "/usr/lib/
result = inContext.theWork()
File "/usr/lib/
File "/usr/lib/
return self.currentCon
File "/usr/lib/
return func(*args,**kw)
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
result = func(*args, **kwargs)
File "/usr/lib/
return func_outside_
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
return func(*args, **kwds)
File "/usr/lib/
return method(params)
File "/usr/lib/
File "/usr/lib/
no longer affects: | maas-images |
no longer affects: | maas/2.6 |
Changed in maas: | |
milestone: | 2.7.0b1 → 2.7.0b2 |
Changed in maas: | |
milestone: | 2.7.0b2 → none |
Additionally, I'm trying to figure out how to remove boot images, however, the documentation only covers how to create these, not remove them:
https:/ /maas.io/ docs/cli- image-managemen t
So I'm left with two broken MAAS environments and no way (that I can see) to resolve this via CLI.