Validation Error raised on RAID devices of a VMHost when refreshing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Triaged
|
High
|
Unassigned |
Bug Description
It appears we throw the following exception when a LXD VMHost with RAID configured refreshes and processes commissioning results:
2022-09-20 16:29:13 metadataserver.api: [critical] seeker02.
Traceback (most recent call last):
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
--- <exception caught here> ---
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
return super().save(*args, **kwargs)
File "/usr/lib/
return super().save(*args, **kwargs)
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
return [
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
raise ValidationError
This particular machine has 4 disks configured into two RAID 1 devices, then those two are configured into a RAID 0. This RAID configuration was created when deploying via MAAS, and did not raise an exception for deployment.
machine-resource output: https:/
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → High |
description: | updated |
Changed in maas: | |
milestone: | none → 3.4.0 |
Changed in maas: | |
milestone: | 3.4.0 → 3.5.0 |
Changed in maas: | |
milestone: | 3.5.0 → 3.5.x |