Re: 答复: CloudStack 4.11.2 Snapshot Revert fail

Hi, Did you try with other OS types - message above suggests that your Xen is seen as 6.5 version and doesn't support CentOS 7 - can you try to edit the VM to CentOS 6 or CentOS 7.1/7.2 etc ? Does the revert works then ? On Wed, 23 Jan 2019 at 02:58, Haijiao <18602198...@163.com> wrote: > This i

Re: Help! Jobs stuck in pending state

Hi Alireza, could you try again after restarting mgt server ? -Wei Alireza Eskandari 于2019年1月23日周三 上午6:22写道： > First I deleted two jobs which was existed in vm_work_job table and its > related entry in sync_queue table but it doesn't help. > Then I delete all the entries in sync_queue tables

答复: 答复: CloudStack 4.11.2 Snapshot Revert fail

I tried, modified the VM to CENTOS6.5 (64-bit) and reported the same error. 发件人: Andrija Panic 发送时间: 2019年1月23日 16:38 收件人: dev 抄送: us...@cloudstack.apache.org 主题: Re: 答复: CloudStack 4.11.2 Snaps

答复: 答复: CloudStack 4.11.2 Snapshot Revert fail

I modified and recompiled cloudstack4.11.2, and then I can complete the xenserver vm snapshot recovery. plugins/hypervisors/xenserver/src/com/cloud/hypervisor/xenserver/resource/CitrixResourceBase.java public VM createWorkingVM(final Connection conn, final String vmName, final String guestOST

Re: 答复: CloudStack 4.11.2 Snapshot Revert fail

Hi I have just reproduced your issue (7.1 though, no updates, and not relevant I guess...) I changed VM (edit VM, while stopped) after it was previously snapshoot-ed successfully OS types vs restore results below: Centos 6.6 x64 fails to restore, CentOS 6.7 x64 fails to restore CentOS 6.5 x64 CAN

Re: Help! Jobs stuck in pending state

I'm following this issue in github: https://github.com/apache/cloudstack/issues/3104 Please leave your comments Thanks On Wed, Jan 23, 2019 at 12:39 PM Wei ZHOU wrote: > Hi Alireza, > > could you try again after restarting mgt server ? > > -Wei > > Alireza Eskandari 于2019年1月23日周三 上午6:22写道： > >

Re: Help! Jobs stuck in pending state

Hi I've had this issue a few times in 2018 and managed to get it fixed pretty easily, although had spent a number of hours initially trying to figure out WTF is going on. This issue looks like one of those artefacts that creeped up in one of the versions released in 2018 and hasn't been address

Re: Help! Jobs stuck in pending state

Hi Alireza, *sync_queue *table is the actual VM sync queue which holds a queue id for each VM (*sync_objtype*: VmWorkJobQueue, *sync_objid*: ) and the VM jobs would reside in *sync_queue_item* table against that queue id. Only one running job is allowed per VM queue (*queue_size_limit*: 1 in *sync

Re: Help! Jobs stuck in pending state

Dear Suresh and Andrei Thanks for your help. I have upgrade CloudStack from 4.9.3 to 4.11.2 but the problem still persists. Then I inspect database tables and I found that these three tables could be the root cause: - op_ha_work - op_lock - vm_work_job So I delete all records in those tables and pr

Re: Why CloudStack 5

Hello Ivan, Can you provide reasons why not move to a version 5? To help you, I will provide why I think we should move to 5.0.0 after 4.12. Therefore, I would expect this 5.0.0 to be an LTS version as well. 1. To begin with, technically, we should already be in version 5 if we had been fol

Re: Why CloudStack 5

Is 4.12 a decent candidate to be branded 5.0 or might we be waiting for some specific set of backwards-incompatible updates? From: Rafael Weingärtner Sent: Wednesday, January 23, 2019 4:58 PM To: dev Cc: users Subject: Re: Why CloudStack 5 NetApp Security WARNI

Re: Why CloudStack 5

I would say that it is indeed a solid version. However, version 4.12 by itself is not breaking anything. Therefore, according to the semantic versioning, we cannot increase the ‘X’ bit. It is also interesting to consider that 4.12 has over 188 PRs merged into it. When we finish, we will probably h

Re: Why CloudStack 5

That sounds reasonable to me. From: Rafael Weingärtner Sent: Wednesday, January 23, 2019 5:25 PM To: users Cc: dev@cloudstack.apache.org Subject: Re: Why CloudStack 5 NetApp Security WARNING: This is an external email. Do not click links or open attachments unl

Re: Why CloudStack 5

I'm in the favour of keeping the 4.x going because no API compatibility is broken, and as long as we are following semver there is no need. Calling a 4.x a 5.x just for the sake of bumping versions may cause some perception issue. Removal of unsupported/poc/incomplete features, plugins including