I have removed 2 hosts from cluster, (I will add 2 again after getting this 
issues fixed) you think that must be causing this?  

When I removed those host I checked all mgmt. logs and XenServer logs for 
errors. There was none.  Also no errors in SSVM logs.

One more thing to notice, is that I have upgrade ACS from 4.4.2 to 4.5.1, after 
that this is first time I am creating new instance in ACS 4.5.1.

I see before that invalid uuid exception these log lines, (sending and 
Executing)

2015-07-13 12:27:17,383 DEBUG [c.c.a.t.Request] (AgentManager-Handler-5:null) 
Seq 4-1439744505875013713: Sending  { Cmd , MgmtId: 249373720971888, via: 4, 
Ver: v1, Flags: 100111, 
[{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"path":"bf6191bb-b55b-493c-b813-df559c03aff2","origUrl":"http://cloudstack.apt-get.eu/systemvm/4.5/systemvm64template-4.5-xen.vhd.bz2","uuid":"9e207d7d-1ecc-427b-82cc-c060ffdd82c7","id":237,"format":"VHD","accountId":2,"checksum":"9cadc145d114d6a8c67d42238f99329d","hvm":true,"displayText":"systemvm-xenserver-4.5","imageDataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"876d490c-a1d4-3bfe-88b7-1bdb2479541b","id":1,"poolType":"NetworkFilesystem","host":"172.16.5.194","path":"/tank/primstore","port":2049,"url":"NetworkFilesystem://172.16.5.194/tank/primstore/?ROLE=Primary&STOREUUID=876d490c-a1d4-3bfe-88b7-1bdb2479541b"}},"name":"237-2-9cc089f5-59bb-3327-a71a-4bbb6b501bc3","hypervisorType":"XenServer"}},"destTO":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"afc1a71d-7143-4182-99eb-dff369c2d8a0","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"876d490c-a1d4-3bfe-88b7-1bdb2479541b","id":1,"poolType":"NetworkFilesystem","host":"172.16.5.194","path":"/tank/primstore","port":2049,"url":"NetworkFilesystem://172.16.5.194/tank/primstore/?ROLE=Primary&STOREUUID=876d490c-a1d4-3bfe-88b7-1bdb2479541b"}},"name":"ROOT-108","size":2684354560,"volumeId":144,"vmName":"r-108-VM","accountId":23,"format":"VHD","provisioningType":"THIN","id":144,"deviceId":0,"hypervisorType":"XenServer"}},"executeInSequence":true,"options":{},"wait":0}}]
 }
2015-07-13 12:27:17,383 DEBUG [c.c.a.t.Request] (AgentManager-Handler-5:null) 
Seq 4-1439744505875013713: Executing:  { Cmd , MgmtId: 249373720971888, via: 4, 
Ver: v1, Flags: 100111, 
[{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"path":"bf6191bb-b55b-493c-b813-df559c03aff2","origUrl":"http://cloudstack.apt-get.eu/systemvm/4.5/systemvm64template-4.5-xen.vhd.bz2","uuid":"9e207d7d-1ecc-427b-82cc-c060ffdd82c7","id":237,"format":"VHD","accountId":2,"checksum":"9cadc145d114d6a8c67d42238f99329d","hvm":true,"displayText":"systemvm-xenserver-4.5","imageDataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"876d490c-a1d4-3bfe-88b7-1bdb2479541b","id":1,"poolType":"NetworkFilesystem","host":"172.16.5.194","path":"/tank/primstore","port":2049,"url":"NetworkFilesystem://172.16.5.194/tank/primstore/?ROLE=Primary&STOREUUID=876d490c-a1d4-3bfe-88b7-1bdb2479541b"}},"name":"237-2-9cc089f5-59bb-3327-a71a-4bbb6b501bc3","hypervisorType":"XenServer"}},"destTO":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"afc1a71d-7143-4182-99eb-dff369c2d8a0","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"876d490c-a1d4-3bfe-88b7-1bdb2479541b","id":1,"poolType":"NetworkFilesystem","host":"172.16.5.194","path":"/tank/primstore","port":2049,"url":"NetworkFilesystem://172.16.5.194/tank/primstore/?ROLE=Primary&STOREUUID=876d490c-a1d4-3bfe-88b7-1bdb2479541b"}},"name":"ROOT-108","size":2684354560,"volumeId":144,"vmName":"r-108-VM","accountId":23,"format":"VHD","provisioningType":"THIN","id":144,"deviceId":0,"hypervisorType":"XenServer"}},"executeInSequence":true,"options":{},"wait":0}}]
 }

I see systemvmteamplate 4.5  is getting called, something new template related 
problem ? I am just guessing all possibilities , I have to get it fixed asap. 


/Sonali

-----Original Message-----
From: Daan Hoogland [mailto:[email protected]] 
Sent: Tuesday, July 14, 2015 3:53 PM
To: [email protected]
Subject: Re: Urgent: VMs not migrated after putting Xenserver host in 
maintenance mode

On Tue, Jul 14, 2015 at 11:49 AM, Sonali Jadhav <[email protected]> 
wrote:
> which uuid is exactly invalid


My first guess would be that cloudstack tries to remove some volume or vm that 
does not exist on the cluster. So xen doesn't know about a uuid that cs is 
providing to xapi

--
Daan

Reply via email to