[2.x, pod] maas cli fails to compose pod after, and doesn't show why
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Medium
|
Unassigned |
Bug Description
Testing in CPE lab, failing to compose pod after pod creation
$ maas admin pod compose 1 hostname=infra-1 cores=1 memory=4096 storage=root:50 zone=1
Unable to compose machine because: Failed talking to pod: sequence item 3: expected str instance, NoneType found
$ maas admin pod compose 1
Unable to compose machine because: Failed talking to pod: sequence item 3: expected str instance, NoneType found
This is 100% reproducible. happens with MAAS 2.2.2
The pod is there...
$ maas admin pods read
Success.
Machine-readable output follows:
[
{
"used": {
},
"name": "infra-1",
"type": "virsh",
"id": 1,
},
],
"total": {
},
]
}
]
Trying to specify a pod that doesn't exist gives a different output, a more expected one...
$ maas admin pod compose 5 hostname=infra-1 cores=1 memory=4096 storage=root:50 zone=1
Not Found
$ maas admin pod compose 5
Not Found
$ dpkg --list | grep maas
ii maas-cli 2.2.2-6099-
ii maas-common 2.2.2-6099-
ii maas-dhcp 2.2.2-6099-
ii maas-dns 2.2.2-6099-
ii maas-proxy 2.2.2-6099-
ii maas-rack-
ii maas-region-api 2.2.2-6099-
ii maas-region-
ii python3-django-maas 2.2.2-6099-
ii python3-maas-client 2.2.2-6099-
ii python3-
tags: | added: cpec |
Changed in maas: | |
milestone: | 2.3.0 → 2.3.x |
Changed in maas: | |
milestone: | 2.3.x → 2.4.x |
Hi Jeff,
I imagine you have a KVM pod. Can you provide more information on how have you installed and configured your libvirt/KVM? Have you created a storage pool, changed the networks, etc?
virsh net-list
virsh pool-list
Also, please provide logs:
/var/log/maas/*.log