I added a glusterfs pool using virsh on a KVM server which is being used as a pod. When I went to refresh the pod in MAAS it failed with a "list index out of range" error. It looks like the virsh pod driver currently only works with directory pool types because other types like gluster don't have the same "path" tag in the xml.
I was able to manually fix the issue by making the following modification in /usr/lib/python3/dist-packages/provisioningserver/drivers/pod/virsh.py, but maybe it would be better to just skip unsupported pool types since gluster won't work with MAAS anyway since it doesn't support volume creation:
75a76
> XPATH_POOL_DIR = "/pool/source/dir"
567d567
< pool_path = evaluator(XPATH_POOL_PATH)[0].text
568a569,574
> if pool_type == 'dir':
> pool_path = evaluator(XPATH_POOL_PATH)[0].text
> elif pool_type == 'gluster':
> pool_path = evaluator(XPATH_POOL_DIR)[0].attrib['path']
> else:
> pool_path = ''
dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-======================================-============-=================================================
ii maas 2.6.0-7802-g59416a869-0ubuntu1~18.04.1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.6.0-7802-g59416a869-0ubuntu1~18.04.1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.6.0-7802-g59416a869-0ubuntu1~18.04.1 all MAAS server common files
ii maas-dhcp 2.6.0-7802-g59416a869-0ubuntu1~18.04.1 all MAAS DHCP server
un maas-dns <none> <none> (no description available)
ii maas-proxy 2.6.0-7802-g59416a869-0ubuntu1~18.04.1 all MAAS Caching Proxy
ii maas-rack-controller 2.6.0-7802-g59416a869-0ubuntu1~18.04.1 all Rack Controller for MAAS
ii maas-region-api 2.6.0-7802-g59416a869-0ubuntu1~18.04.1 all Region controller API service for MAAS
ii maas-region-controller 2.6.0-7802-g59416a869-0ubuntu1~18.04.1 all Region Controller for MAAS
un maas-region-controller-min <none> <none> (no description available)
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-maas-provisioningserver <none> <none> (no description available)
ii python3-django-maas 2.6.0-7802-g59416a869-0ubuntu1~18.04.1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.6.0-7802-g59416a869-0ubuntu1~18.04.1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.6.0-7802-g59416a869-0ubuntu1~18.04.1 all MAAS server provisioning libraries (Python 3)
Is this still an issue in a recent MAAS (3.3+)?