backtrace when creating bcached partition
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
High
|
Unassigned | ||
1.9 |
Won't Fix
|
High
|
Unassigned |
Bug Description
When creating a new bcached partition via the MAAS UI, after I click the final "Create bcache", nothing seems to happen, except that the bcache UI, including the device I selected, disappear. But I note the following in regiond.log:
2016-04-18 02:02:02 [-] Error on request (345) node.create_bcache: <ul class="
Traceback (most recent call last):
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
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/
raise HandlerError(
This seems similar to https:/
We are running MAAS 1.9.1+bzr4543-
Changed in maas: | |
importance: | Undecided → High |
milestone: | none → 2.0.0 |
status: | New → Triaged |
I've discovered that if I create an unformatted partition manually, select the resulting (in this case) "sda-part3", and invoke "create bcache", then everything works fine.
I think the MAAS UI should either do this for me, or else prevent me from invoking "create bcache" on the unformatted space of a block device perhaps with some kind of hint. But the first option seems friendlier.