kevin parker created CLOUDSTACK-1225:
----------------------------------------

             Summary: Storage System vm id keeps on increasing 
                 Key: CLOUDSTACK-1225
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1225
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Install and Setup
    Affects Versions: 4.0.1
         Environment: Cloud Stack Mgmnt server 4.0.1 :XCP Virtual Machine 
running with CentOS release 6.2 (Final)/ 2.6.32-220.el6.x86_64
Mysql:5.1.67,Host: XCP Host 1.4.90-53341c,Storage: both primary and secondary 
is on management server (/export/primary and /export/secondary),ip address: 
Every machine is having public ip in the same CIDR.
            Reporter: kevin parker
            Priority: Minor


Its been 3 weeks since i am working on Cloud Stack 4.0.1 
(http://jenkins.cloudstack.org/view/4.0.1/job/build-4.0.1-nonoss-rhel63/)  but 
couldn't even start system vms..I UI its showing "Creating system VMs (this may 
take a while)" but nothing is happening and i also noticed that  

select * from cloud.vm_instance\G;  is increasing every minute. every 
minute-two new id is getting generated in state Expunging.

But In UI its is still trying to create system VM but is failing but there is 
no way to alert user about this.Will this ever stop?

 Exception while trying to start secondary storage vm
com.cloud.exception.InsufficientServerCapacityException: Unable to create a 
deployment for VM[SecondaryStorageVm|s-91-VM]Scope=interface 
com.cloud.dc.DataCenter; id=1
2013-02-11 08:15:59,375 WARN  [cloud.api.ApiDispatcher] (Job-Executor-8:job-8) 
class com.cloud.api.ServerApiException : Fail to start system vm

this is the log:http://pastebin.com/fE5uUgZt


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to