Ask Your Question
2

Remove Istance with Error status

asked 2014-08-16 12:11:14 -0600

New-stack gravatar image

hi people... i wrongly created these instance on a server, which don't exist (lol)

# nova list
+--------------------------------------+---------------+--------+------------+-------------+----------+
| ID                                   | Name          | Status | Task State | Power State | Networks |
+--------------------------------------+---------------+--------+------------+-------------+----------+
| 3cb7546b-9972-4b25-b7fa-5d9501b160a2 | demo-instace1 | ERROR  | deleting   | NOSTATE     |          |
| 9836fd3f-fba8-44cb-ad37-ca05fac4227b | demo-instace1 | ERROR  | deleting   | NOSTATE     |          |
| a5717bbb-e59a-418d-bd7a-a625d8cf3201 | demo-instace1 | ERROR  | deleting   | NOSTATE     |          |
| c4d9e75f-2e88-4eb3-b802-58694db96862 | demo-instace1 | ERROR  | deleting   | NOSTATE     |          |
+--------------------------------------+---------------+--------+------------+-------------+----------+

i try to delete all of this instance with nova delete id/name command, but unsuccessful! I try also nova reset-state --active id/name instance....but unsuccessful! Are there other way to delete correctly those instance o i have to delete this manually from db?

Thanks all

edit retag flag offensive close merge delete
add a comment

3 answers

Sort by ยป oldest newest most voted
1

answered 2014-08-18 05:13:54 -0600

foexle gravatar image

Hi,

  • check on which compute node these instances was booted
  • check if all images are deleted (otherwise will reep the compute service later)
  • search these 3 instances by ID in your DB
  • update these 3 rows (DB) and marked as "deleted=t"
  • check on your compute nodes if you get warnings like [..]Found 6 in the database and 5 on the hypervisor[..]

If it's gone congrats :).... next check why this error occurs, normally your compute service doesn't report to your messeging bus.

Cheers Heiko

edit flag offensive delete link more

Comments

i try to do:

update instances set deleted='t' where display_name='instance_name';

but i have 4 warning e 0 changed rows....

New-stack gravatar imageNew-stack ( 2014-08-19 05:23:29 -0600 )edit
add a comment
1

answered 2014-08-18 01:13:13 -0600

achutha gravatar image

stop all services and delete the database again start all the services one by one . you can able to delete.

edit flag offensive delete link more

Comments

Maybe in a testing env, not in a production :)

foexle gravatar imagefoexle ( 2014-08-18 05:09:57 -0600 )edit

all service on controller? Doing this,all cloud crash?

New-stack gravatar imageNew-stack ( 2014-08-18 11:06:07 -0600 )edit

hi foexle you are right in testing environment it will works but in production environment it is not the right way could you post your configuration files of nova.

achutha gravatar imageachutha ( 2014-08-18 23:17:57 -0600 )edit

by stopping the services in nova threre is no damage but in production environment it will be a mistake?

achutha gravatar imageachutha ( 2014-08-18 23:19:31 -0600 )edit
add a comment
0

answered 2014-08-18 10:50:44 -0600

New-stack gravatar image

updated 2014-08-18 10:56:53 -0600

Thanks at all...

check on which compute node these instances was booted (Howto?)

I have never seen the instance on...may be because the building process is never completly finished! :) I try to run my first instance...

check if all images are deleted

cinder list is empty

update these 3 rows (DB) and marked as "deleted=t"

I have run this query on my db:

select id,display_name,host,vm_state,task_state,progress,node,deleted from instances;
+----+---------------+----------------------+----------+------------+----------+----------------------+---------+
| id | display_name  | host                 | vm_state | task_state | progress | node                 | deleted |
+----+---------------+----------------------+----------+------------+----------+----------------------+---------+
|  1 | try_to_try    | NULL                 | building | deleting   |        0 | NULL                 |       1 |
|  2 | demo-instace1 | NULL                 | building | deleting   |        0 | NULL                 |       2 |
|  3 | demo-instace1 | NULL                 | building | deleting   |        0 | NULL                 |       3 |
|  4 | demo-instace1 | cloud99it | error    | deleting   |        0 | cloud99it |       0 |
|  5 | demo-instace1 | cloud99it | error    | deleting   |        0 | cloud99it |       0 |
|  6 | demo-instace1 | cloud99it | error    | deleting   |        0 | cloud99it |       0 |
|  7 | demo-instace1 | cloud99it | error    | deleting   |        0 | cloud99it |       0 |
+----+---------------+----------------------+----------+------------+----------+----------------------+---------+

First to update "deleted=t", how can I select the host on witch run the instance? I have 2 compute nodes... the first is a physical one and the second is virtual one... cloud99it is the first node and it's unplugged to the network: for this reason i wan to run the instance on cloud100...

and yes, this is a testing env

edit flag offensive delete link more
add a comment

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

subscribe to rss feed

Stats

Asked: 2014-08-16 12:11:14 -0600

Seen: 149 times

Last updated: Aug 18 '14

Related questions

Heat stack with unreachable resource stuck in failed state

ERROR oslo.messaging._drivers.impl_rabbit [-] AMQP server on 192.168.0.106:5672 is unreachable: [Errno 111] ECONNREFUSED.

OSA deployment fail in setup-infraestrucure.yml

First Instance Error: No hosts matched due to not matching 'force_hosts' value of 'compute100'

RDO Error: php56w-common conflicts with php-common-5.4.16-36.el7_1.x86_64

instance not starting with libvirt-type set to qemu

Cinder volume goes to error state [closed]

Error in the installation of nova compute service on the controller node

openstack High Availability corosync API error 2

Connection timed out when running nova image-list