PartionTable matching query does not exist
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
New
|
Undecided
|
Unassigned |
Bug Description
On Rod Smiths home AMT setup using MAAS Version 1.9.0 (alpha5+bzr4383), I am able to deploy the node fine but when I go to commission it I run into this (it was already commissioned when I first tried using it):
2015-10-25 21:46:29 [-] Error on request (338) node.action: PartitionTable matching query does not exist.
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
self.run()
File "/usr/lib/
self.
File "/usr/lib/
return super(ThreadPool, self)._worker()
--- <exception caught here> ---
File "/usr/lib/
result = context.call(ctx, function, *args, **kwargs)
File "/usr/lib/
return self.currentCon
File "/usr/lib/
return func(*args,**kw)
File "/usr/lib/
return func_outside_
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
return action.
File "/usr/lib/
skip_
File "/usr/lib/
return func_within_
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
self.
File "/usr/lib/
block_
File "/usr/lib/
collector.
File "/usr/lib/
sender=model, instance=obj, using=self.using
File "/usr/lib/
response = receiver(
File "/usr/lib/
partition_
File "/usr/lib/
rel_obj = qs.get()
File "/usr/lib/
self.
maasserver.
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 1.9.0~alpha5+
ii maas-cert-server 0.2.6-0~
ii maas-cli 1.9.0~alpha5+
ii maas-cluster-
ii maas-common 1.9.0~alpha5+
ii maas-dhcp 1.9.0~alpha5+
ii maas-dns 1.9.0~alpha5+
ii maas-proxy 1.9.0~alpha5+
ii maas-region-
ii maas-region-
ii python-django-maas 1.9.0~alpha5+
ii python-maas-client 1.9.0~alpha5+
ii python-
As further information, this problem occurs when switching between the disk-use types (flat, LVM, and bcache). Sticking to the default type of LVM causes the bug to not occur. It can be worked around by manually removing all the partition assignments using the MAAS web UI.