<div dir="ltr"><div>From time to time (in particular where there are problems with the Rabbit cluster) I also see this problem. In such cases I "mark" the instance as deleted in the database. I don't know if there are cleaner solutions</div><div><br></div><div>Cheers, Massimo</div><div><br></div><div>[*]</div>update instances set deleted=1 where uuid="<vm-uuid>";<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 22, 2020 at 7:35 AM Szabo, Istvan (Agoda) <<a href="mailto:Istvan.Szabo@agoda.com">Istvan.Szabo@agoda.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The problem is that in opestack you can't find this vm if I want to delete:<br>
<br>
<br>
nova reset-state 94ab55d3-3e39-48d3-a9b2-505838ceb6e7 --active<br>
Reset state for server 94ab55d3-3e39-48d3-a9b2-505838ceb6e7 failed: No server with a name or ID of '94ab55d3-3e39-48d3-a9b2-505838ceb6e7' exists.<br>
ERROR (CommandError): Unable to reset the state for the specified server(s).<br>
<br>
<br>
openstack server delete 94ab55d3-3e39-48d3-a9b2-505838ceb6e7<br>
No server with a name or ID of '94ab55d3-3e39-48d3-a9b2-505838ceb6e7' exists.<br>
<br>
<br>
nova force-delete 94ab55d3-3e39-48d3-a9b2-505838ceb6e7<br>
ERROR (CommandError): No server with a name or ID of '94ab55d3-3e39-48d3-a9b2-505838ceb6e7' exists.<br>
<br>
<br>
openstack server delete hk-qaciapp-2020<br>
No server with a name or ID of 'hk-qaciapp-2020' exists.<br>
<br>
<br>
But if I list it like this can see:<br>
<br>
openstack server list --all-projects --long --limit -1 | grep 94ab55d3-3e39-48d3-a9b2-505838ceb6e7<br>
| 94ab55d3-3e39-48d3-a9b2-505838ceb6e7 | hk-qaciapp-2020 | BUILD | scheduling | NOSTATE | | CentOS-7-x86_64-1511 (14.11.2017) | 2caaef01-e2f9-4e93-961a-c2b2d4a6be82 | QA_VLAN62 | None |<br>
<br>
<br>
:/<br>
<br>
<br>
It was created with the api before, maybe should try to delete with the API? Not sure :/<br>
<br>
________________________________<br>
From: Ignazio Cassano <<a>ignaziocassano@gmail.com</a>><br>
Sent: Tuesday, September 22, 2020 12:21 PM<br>
To: Szabo, Istvan (Agoda)<br>
Cc: openstack-discuss<br>
Subject: Re: Can't delete a vm<br>
<br>
Email received from outside the company. If in doubt don't click links nor open attachments!<br>
________________________________<br>
Hello, before feeling instance, try to use nova reset-state to change the state of in instance to available.<br>
Then try to remove.<br>
Ignazio<br>
<br>
Il Mar 22 Set 2020, 06:43 Szabo, Istvan (Agoda) <<a>Istvan.Szabo@agoda.com</a><mailto:<a>Istvan.Szabo@agoda.com</a>>> ha scritto:<br>
Hello,<br>
<br>
<br>
I have vm which is stuck in the build phase:<br>
<br>
<br>
openstack server list --all-projects --long --limit -1 | grep 94ab55d3-3e39-48d3-a9b2-505838ceb6e7 | 94ab55d3-3e39-48d3-a9b2-505838ceb6e7 | hk-qaciapp-2020 | BUILD | scheduling | NOSTATE | | CentOS-7-x86_64-1511 (14.11.2017) | 2caaef01-e2f9-4e93-961a-c2b2d4a6be82 | QA_VLAN62 | None<br>
<br>
<br>
I've tried to delete with openstack server delete, nova delete force, restarted the nova services on all management nodes, restarted the nova compute service where it was originally spawned but still visible.<br>
<br>
<br>
I see in the database in couple of places either the id and either the hostname, like in instance mapping table, instances table, nova_cell0 database ...<br>
<br>
<br>
I have an idea how to delete, so I'd spawn just a vm and check which tables are created the entries, and I would go through all tables with the problematic one and delete 1 by 1 but this will takes me hours ....<br>
<br>
Any faster way you might suggest me please?<br>
<br>
<br>
Thank you<br>
<br>
<br>
________________________________<br>
This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.<br>
<br>
<br>
</blockquote></div>