cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wei ZHOU <ustcweiz...@gmail.com>
Subject Re: Unable to create instance after upgrading to CloudStack 4.2.0
Date Wed, 02 Oct 2013 14:47:20 GMT
For a temporary solution, log in the database, try again after run
insert into resource_count(domain_id,type) select id,"cpu" from domain;
insert into resource_count(domain_id,type) select id,"memory" from domain;
insert into resource_count(domain_id,type) select id,"primary_storage" from
domain;
insert into resource_count(domain_id,type) select id,"secondary_storage"
from domain;
insert into resource_count(account_id,type) select id,"cpu" from account;
insert into resource_count(account_id,type) select id,"memory" from account;
insert into resource_count(account_id,type) select id,"primary_storage"
from account;
insert into resource_count(account_id,type) select id,"secondary_storage"
from account;



2013/10/2 Valery Ciareszka (JIRA) <jira@apache.org>

>
> [ https://issues.apache.org/jira/browse/CLOUDSTACK-4627?
> page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&
> focusedCommentId=13784006#comment-13784006 ]
>
> Valery Ciareszka commented on CLOUDSTACK-4627:
> ----------------------------------------------
>
> Was it really commited to 4.2.0 branch ? I see old version in latest
> source package:
>
> wget http://www.eu.apache.org/dist/cloudstack/releases/4.2.0/
> apache-cloudstack-4.2.0-src.tar.bz2
> tar jxfv apache-cloudstack-4.2.0-src.tar.bz2
>
> [root@ad011d apache-cloudstack-4.2.0-src]# grep -A9
> canVmRestartOnAnotherServer
> server/src/com/cloud/storage/VolumeManagerImpl.java
> public boolean canVmRestartOnAnotherServer(long vmId) {
> List<VolumeVO> vols = _volsDao.findCreatedByInstance(vmId);
> for (VolumeVO vol : vols) {
> if (!vol.isRecreatable() && !vol.getPoolType().isShared()) {
> return false;
> }
> }
> return true;
> }
>
>
> > HA not working, User VM wasn't Migrated
> > ---------------------------------------
> >
> > Key: CLOUDSTACK-4627
> > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4627
> > Project: CloudStack
> > Issue Type: Bug
> > Security Level: Public(Anyone can view this level - this is the default.)
> > Components: Hypervisor Controller, KVM, Management Server
> > Affects Versions: 4.2.0
> > Environment: CentOS 6.3 64bit
> > Reporter: Naoki Sakamoto
> > Assignee: edison su
> > Attachments: 20130906_HA_SystemVM_Migration_OK_But_UserVM_NG.zip,
> 20130909_HA_UserVM_Migration_NG.zip
> >
> >
> > 1. We made one of KVM Host Power OFF by push power button of hardware
> for High Availability Test.
> > 2. Vritual Router / Secodary Storage VM / Console Proxy VM is Migrated.
> > But User VM wasn't Migrated.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.1#6144)
>



2013/10/2 Indra Pramana <indra@sg.or.id>

> Hi Wei Zhou,
>
> Thanks for your e-mail.
>
> Do you have any recommendation or suggestion on how we can resolve the
> problem? I am not a CloudStack developer (just a normal user) so we are at
> loss on how we can resolve this issue. We are not able to upgrade to 4.2.0
> because of this new problem, after we managed to get around quite a lot of
> bumps on our road to 4.2.0.
>
> Looking forward to your reply, thank you.
>
> Cheers.
>
>
>
> On Wed, Oct 2, 2013 at 10:25 PM, Wei ZHOU <ustcweizhou@gmail.com> wrote:
>
> > Hi Indra,
> >
> > It is a java file, not a script.
> >  ./server/src/com/cloud/server/ConfigurationServerImpl.java
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message