If the machine is acquired, partition filesystems created from the storage layouts are not returned from "maas $profile partitions read"
The reason is the logic in maasserver.utils.storage:get_effective_filesystem(), which has the following comment:
A `BlockDevice` or `Partition` can have up to two `Filesystem` one with
`acquired` set to False and another set to `True`. When the `Node` for
`model` is in an allocated state the acquired `Filesystem` will be used
over the non-acquired `Filesystem`.
Filesystems created by storage layouts are never marked as acquired, so they're never returned if the machine is acquired.
I'm not exactly sure about the logic behind this, and whether this is intentional or a bug.
This affects API as well as UI.
If the machine is acquired, partition filesystems created from the storage layouts are not returned from "maas $profile partitions read"
The reason is the logic in maasserver. utils.storage: get_effective_ filesystem( ), which has the following comment:
A `BlockDevice` or `Partition` can have up to two `Filesystem` one with
`acquired` set to False and another set to `True`. When the `Node` for
`model` is in an allocated state the acquired `Filesystem` will be used
over the non-acquired `Filesystem`.
Filesystems created by storage layouts are never marked as acquired, so they're never returned if the machine is acquired.
I'm not exactly sure about the logic behind this, and whether this is intentional or a bug.