| Danysan1 | |
| Tue, Jul 21, 10:57 AM |
| F95026241: image.png | |
| Tue, Jul 21, 10:57 AM |
| F95027315: image.png | |
| Tue, Jul 21, 10:57 AM |
| F95026194: image.png | |
| Tue, Jul 21, 10:57 AM |
Three days and half ago I created inside the osmit project the osmit-estratti-trixie instance. I would expect it to be up and running by now, but to this moment it is still in the "Planning" task / "Build" state:
I tried checking the logs to debug this problem but I wasn't able to do it because the Logs tab shows an error (direct link here):
What's the problem blocking the instance here? Is there something I can do to unlock this instance or do I need to destroy and re-create it?
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Danysan1 | T429722 Cloud VPS osmit-estratti: upgrade Debian bullseye -> trixie | |||
| Resolved | BUG REPORT | Danysan1 | T432712 Instance still in planning after three days |
I noticed the -trixie instance has hostname osmit-estratti and found this in the logs
/var/log/nova/nova-conductor.log.4.gz:2026-07-17 21:38:33.193 3648 ERROR oslo_messaging.rpc.server [None req-a9c16ea7-dfc3-43e2-8074-11fcbb6ad948 dsantini osmit - - default default] Exception during message handling: nova.exception.InstanceExists: Instance osmit-estratti already exists. /var/log/nova/nova-conductor.log.4.gz:2026-07-17 21:38:33.193 3648 ERROR oslo_messaging.rpc.server nova.exception.Instan ceExists: Instance osmit-estratti already exists.
Please delete the instance and try again, not sure how the hostname without the -trixie suffix got there
Another instance with the name osmit-estratti exists in the same project.
I had created that instance with the intention of using another name but by mistake I used the same and the horizon interface didn't stop me. When I realized, I renamed the instance to osmit-estratti-trixie. So I guess that the problem was either caused by the initial creation with the same name as an existing instance (in this case horizon should have stopped me before creating it) or the later renaming.
Either way, I deleted and re-created the instance, this time with the correct name, and it started without problems and I managed to connect via SSH, so the problem is resolved. Thanks.