Oliver, Please ignore my previous message. I got confused with a different OpenStack Topic… You can follow my suggestions below.. It seems that the error you are getting is related to the node group ID not being found. This could happen for “several reasons” as you know such as: • if node group ID is incorrect or does not exist in the database. • deleted or renamed after creating the cluster template. • node group ID is not specified in the cluster template parameters. To troubleshoot for this, you can try the following steps: - Check the node group ID that you are passing to the openstack coe cluster create command. Make sure it matches the one in your cluster template and database. - Check the status of your cluster template and node groups using openstack coe cluster list and openstack coe nodegroup list. See if they are created, updated, or failed. - Check the logs of your magnum-conductor service using journalctl -u magnum-conductor. Look for any errors or warnings related to node groups or clusters. If you share different logs according to these, we can find a clearer solution, i guess. Kerem ÇELİKER Head of Cloud Infrastructure tr.linkedin.com/in/keremceliker


Sevgiler,
Best,
Kerem ÇELİKER


On Mon, Dec 18, 2023 at 10:53 KEREM CELIKER <kmceliker@gmail.com> wrote:
Hey Oliver,

it seems that the error is caused by a node group ID not being found in the database. This could happen if the node group was deleted or never created in the first place.

Here are some possible ways to fix this issue:

• You can try to recreate the node group using the nova-manage nodegroup create command with the same name and UUID as the one you are trying to use.

• if the node group exists in the database by using the nova-manage nodegroup list command and look for the one with the matching UUID.

• verify that you have created a cluster template with a valid node group ID and that it matches the one you are trying to use.You can

• check if there are any other processes or services that are using or locking the node group ID and terminate them.

I hope this helps you resolve your problem, mate :)

Cheers,
Best,
Kerem Çeliker
Head of Cloud Architecture
tr.linkedin.com/in/keremceliker