> The placement service for keystone.openstack.maas:RegionOne exists but does not have any supported versions
> nova-cloud-controller 24.0.0 active 3 nova-cloud-controller stable 363 no Unit is ready
> placement 6.0.0 active 3 placement stable 32 no Unit is ready
according to the versions from juju status you are running focal-xena, although the current version of python3-nova in the archive is 24.2.0 , I don't think this is the root cause, but this is something you should consider.
what's the endpoint registered for the placement service?, you can run "openstack endpoint list | grep placement" to get it.
Also check, in the placement units, the logs available at /var/log/placement/placement_*.log .
I will mark the bug as 'incomplete', but feel free to change it back to 'New' once you have more insights to share about your cloud.
Hi Mario,
Thanks for filing this bug.
> The placement service for keystone. openstack. maas:RegionOne exists but does not have any supported versions
> nova-cloud- controller 24.0.0 active 3 nova-cloud- controller stable 363 no Unit is ready
> placement 6.0.0 active 3 placement stable 32 no Unit is ready
according to the versions from juju status you are running focal-xena, although the current version of python3-nova in the archive is 24.2.0 , I don't think this is the root cause, but this is something you should consider.
what's the endpoint registered for the placement service?, you can run "openstack endpoint list | grep placement" to get it.
Also check, in the placement units, the logs available at /var/log/ placement/ placement_ *.log .
I will mark the bug as 'incomplete', but feel free to change it back to 'New' once you have more insights to share about your cloud.
Best,