Pod manager counts all virsh pools as available disk

On my laptop virsh is configured to have access to two pools which are two different directories on my system. I added virsh as a pod to MAAS but it thinks my system has double the amount of disk space. MAAS should recognize that both pools are on the same disk and only count it once.

$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/ubuntu--vg-root 463423296 280780180 159079444 64% /
/dev/sda2 241965 138970 90503 61% /boot
/dev/sda1 121982 3496 118486 3% /boot/efi

$ maas maas pods read
Success.
Machine-readable output follows:
[
    {
        "id": 1,
        "available": {
            "memory": 9778,
            "cores": 2,
            "local_storage": 914720659864
        },
        "name": "suited-gopher",
        "architectures": [
            "amd64/generic"
        ],
        "used": {
            "memory": 6144,
            "cores": 6,
            "local_storage": 34359738368
        },
        "type": "virsh",
        "resource_uri": "/MAAS/api/2.0/pods/1/",
        "capabilities": [
            "composable",
            "dynamic_local_storage",
            "over_commit"
        ],
        "total": {
            "memory": 15922,
            "cores": 8,
            "local_storage": 949080398232
        }
    }
]

$ virsh pool-list
 Name State Autostart
-------------------------------------------
 default active yes
 ISOs active yes

$ virsh pool-info default
Name: default
UUID: f2bb24f2-deca-4f87-a09d-b7eb9677671d
State: running
Persistent: yes
Autostart: yes
Capacity: 441.95 GiB
Allocation: 267.05 GiB
Available: 174.90 GiB

$ virsh pool-info ISOs
Name: ISOs
UUID: 109ba190-305d-44de-ab05-e64da6e7ae53
State: running
Persistent: yes
Autostart: yes
Capacity: 441.95 GiB
Allocation: 267.05 GiB
Available: 174.90 GiB