Donal Lafferty created CLOUDSTACK-5439:
------------------------------------------
Summary: CloudStack does not deal with existing Hyper-V System VMs
Key: CLOUDSTACK-5439
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5439
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Hypervisor Controller
Affects Versions: 4.3.0
Reporter: Donal Lafferty
I started a Hyper-V zone, which deployed a secondary storage VM to my Hyper-V
host.
Later, I stopped the management server, deleted the database, and restarted the
database server. I applied the same configuration script.
This time, the management server seemed to get stuck trying to connect to the
agent on the existing secondary storage. I saw the following message appear
multiple times in vmops.log:
2013-12-10 13:15:26,997 DEBUG [c.c.s.StatsCollector]
(StatsCollector-1:ctx-c483bea4) HostStatsCollector is running...
2013-12-10 13:15:26,999 DEBUG [c.c.s.StatsCollector]
(StatsCollector-2:ctx-a2557e88) VmStatsCollector is running...
2013-12-10 13:15:27,005 DEBUG [c.c.s.StatsCollector]
(StatsCollector-3:ctx-6520624e) StorageCollector is running...
2013-12-10 13:15:31,243 WARN [c.c.u.n.Link] (AgentManager-Selector:null) SSL:
Fail to find the generated keystore. Loading fail-safe one to continue.
2013-12-10 13:15:32,129 DEBUG [c.c.a.t.Request] (AgentManager-Handler-7:null)
Seq 0-0: Scheduling the first command { Cmd , MgmtId: -1, via: 0, Ver: v1,
Flags: 101,
[{"com.cloud.agent.api.StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","id":0,"version":"4.3.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"10.70.176.132","publicNetmask":"255.255.240.0","publicMacAddress":"06:56:a4:00:00:12","privateIpAddress":"10.70.176.93","privateMacAddress":"06:de:9a:00:00:04","privateNetmask":"255.255.240.0","storageIpAddress":"10.70.176.93","storageNetmask":"255.255.240.0","storageMacAddress":"06:de:9a:00:00:04","resourceName":"NfsSecondaryStorageResource","wait":0}}]
}
2013-12-10 13:15:32,137 DEBUG [c.c.a.t.Request]
(AgentConnectTaskPool-2:ctx-10fb889d) Seq 0-0: Processing the first command {
Cmd , MgmtId: -1, via: 0, Ver: v1, Flags: 101,
[{"com.cloud.agent.api.StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","id":0,"version":"4.3.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"10.70.176.132","publicNetmask":"255.255.240.0","publicMacAddress":"06:56:a4:00:00:12","privateIpAddress":"10.70.176.93","privateMacAddress":"06:de:9a:00:00:04","privateNetmask":"255.255.240.0","storageIpAddress":"10.70.176.93","storageNetmask":"255.255.240.0","storageMacAddress":"06:de:9a:00:00:04","resourceName":"NfsSecondaryStorageResource","wait":0}}]
}
2013-12-10 13:15:32,144 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentConnectTaskPool-2:ctx-10fb889d) Failed to handle host connection:
java.lang.IllegalArgumentException: Host 10.70.176.93 sent incorrect data
center: 1
2013-12-10 13:15:32,149 WARN [c.c.a.m.AgentManagerImpl]
(AgentConnectTaskPool-2:ctx-10fb889d) Unable to create attache for agent: Seq
0-0: { Cmd , MgmtId: -1, via: 0, Ver: v1, Flags: 101,
[{"com.cloud.agent.api.StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","id":0,"version":"4.3.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"10.70.176.132","publicNetmask":"255.255.240.0","publicMacAddress":"06:56:a4:00:00:12","privateIpAddress":"10.70.176.93","privateMacAddress":"06:de:9a:00:00:04","privateNetmask":"255.255.240.0","storageIpAddress":"10.70.176.93","storageNetmask":"255.255.240.0","storageMacAddress":"06:de:9a:00:00:04","resourceName":"NfsSecondaryStorageResource","wait":0}}]
}
2013-12-10 13:15:32,240 WARN [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-8:null) Throwing away a request because it came through
as the first command on a connect: Seq 0--1: { Cmd , MgmtId: -1, via: 0, Ver:
v1, Flags: 111,
[{"com.cloud.agent.api.ShutdownCommand":{"reason":"sig.kill","wait":0}}] }
2013-12-10 13:15:32,247 WARN [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-9:null) Throwing away a request because it came through
as the first command on a connect: Seq 0-1: { Cmd , MgmtId: -1, via: 0, Ver:
v1, Flags: 11,
[{"com.cloud.agent.api.PingStorageCommand":{"changes":{},"hostType":"Storage","hostId":0,"wait":0}}]
}
2013-12-10 13:15:33,190 INFO [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-10:null) Connection from /10.70.176.93 closed but no
cleanup was done.
2013-12-10 13:15:40,875 DEBUG [c.c.c.ConsoleProxyManagerImpl]
(consoleproxy-1:ctx-fe8996d6) Skip capacity scan due to there is no Primary
Storage UPintenance mode
2013-12-10 13:15:42,022 DEBUG [c.c.a.AlertManagerImpl]
(CapacityChecker:ctx-2aa2b4e9) Running Capacity Checker ...
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
