欧卡2中文社区

 找回密码
 立即注册

QQ登录

只需一步,快速开始

需要三步,才能开始

只需两步,慢速开始

玩欧卡就用莱仕达V10方向盘欧卡2入门方向盘选莱仕达V9莱仕达折叠便携游戏方向盘支架欢迎地图Mod入驻
查看: 4195|回复: 0
收起左侧

We cannot stop VM[ConsoleProxy|v-*-VM] when it is in state Starting

[复制链接]
oppo 发表于 2015-4-3 11:10 | 显示全部楼层 |阅读模式
Hi all,

I have the following issue:
After emergency reboot of hypervisor node (i.e. reset via ipmi), system vms
got stuck in "starting state":


When I look onto console through vnc I see either prompt for fsck or errors
related to r/o mounted root fs:


There is no way to destroy vm either from web interface or api
(cloudmonkey):

 cloudmonkey> destroy systemvm id=eb3adb37-96d1-4785-884d-5958526b75fc
Async query failed for jobid 3c2fd0d7-a0a0-427a-ae3e-dda96b7cf9e0
Error 530 We cannot stop VM[ConsoleProxy|v-1058-VM] when it is in state
Starting
 cloudmonkey>

I have to manually update state in mysql before I am able to destroy this
vm:

mysql> update vm_instance set state='Stopped' where name='v-1058-VM';
\Query OK, 1 row affected (0.08 sec)
Rows matched: 1  Changed: 1  Warnings: 0

 cloudmonkey> destroy systemvm id=eb3adb37-96d1-4785-884d-5958526b75fc
.



....


...............



................

..............................................................





accountid =
b080d9c2-c3b2-4ffd-8a1c-04e99d03f5ef.......................................................
cmd = com.cloud.api.commands.DestroySystemVmCmd
created = 2013-04-16T14:54:47+0200
jobid = 23942741-a26c-4dba-b65b-1a4536aab1d7
jobprocstatus = 0
jobresult:
=========
systemvm:
========
id = eb3adb37-96d1-4785-884d-5958526b75fc
created = 2013-04-16T13:02:03+0200
dns1 = 8.8.8.8
hostid = b069e873-675b-435d-a7f1-a7edf87ce9b1
hostname = ad112.colobridge.net
name = v-1058-VM
objectId = 1058
podid = f04bddae-fd73-47ac-b40e-32a4d2a8b7d5
state = Stopped
systemvmtype = consoleproxy
templateid = e54cbb23-bc5b-48d1-925b-1225ef938ea4
zoneid = 6ff79c9f-eccc-466f-9d43-3ce941855002
zonename = Zone1
jobresultcode = 0
jobresulttype = object
jobstatus = 1
userid = 79c285d1-54df-4169-84d1-72ff99f52998


First question is: why cloudstack does not handle such vm start errors ?

Second question is: how to force deletion of such VMs without mysql hack ?

environment:
CS 4.0.1, Centos 6.4 (management+node1+node2), OpenIndiana NFS server as
primary and secondary storage
--
Regards,
Valery

http://protocol.by/slayer

联系我们|手机版|欧卡2中国 ( 湘ICP备11020288号-1 )

GMT+8, 2024-4-19 05:31 , Processed in 0.035127 second(s), 9 queries , Redis On.

Powered by Discuz! X3.4

Copyright © 2001-2023, Tencent Cloud.

快速回复 返回顶部 返回列表