Re: failed 430-440 upgrade: Unable to start instance due to Unable to get answer that is of class com.cloud.agent.api.StartAnswer

On 10/21/2014 12:36 AM, Nux! wrote: > Wido, > > Alas DEBUG is on without telling me anything I can understand. Here's some > more: > > http://pastebin.com/raw.php?i=cYf8g5tg > So this is the issue: 2014-10-20 23:24:27,323 DEBUG [cloud.agent.Agent] (agentRequest-Handler-1:null) Seq 1-1609755

commits on 4.5

David, I keep seeing commits passing to the 4.5 branch. As you are the RM I am not reverting them. Should I? Not one of them has come from a hotfix branch for weeks. -- Daan

Re: [PROPOSAL] Move to github PR only during moratorium on commit

On Oct 21, 2014, at 6:32 AM, Mike Tutkowski wrote: > Code reviews are great. > > However, we will need to change our behavior quite a bit if code is to make > it in within a reasonable amount of time as code reviews today often don't > get done in a timely fashion. Just look at it as an incr

Re: [PROPOSAL] Move to github PR only during moratorium on commit

Ok, no one says it so let me be the bad guy. Nothing will work unless the citrix department in california agrees. They have their in-house legacy proces to change and will not unless they can sell it easily upstream. So whether we make a grand uninfied proposal or take small steps doesn't matter,

Re: [PROPOSAL] Move to github PR only during moratorium on commit

On Oct 21, 2014, at 9:36 AM, Daan Hoogland wrote: > Ok, no one says it so let me be the bad guy. > > > Nothing will work unless the citrix department in california agrees. They > have their in-house legacy proces to change and will not unless they can > sell it easily upstream. So whether we m

pre-announcement of release 4.4.1

H devs, as the finalisation of the release announcement is taking some time, here is the sneak preview: = = = [APACHE CLOUDSTACK LOGO] Announcing Apache™ CloudStack™ v4.4.1 Mature, easy-to-deploy Open Source Cloud computing software platform boasts improved efficiency and performance. [DATELIN

Re: failed 430-440 upgrade: Unable to start instance due to Unable to get answer that is of class com.cloud.agent.api.StartAnswer

Thanks Wido, I'll attempt another upgrade tonight. Cheers! -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Wido den Hollander" > To: dev@cloudstack.apache.org > Sent: Tuesday, 21 October, 2014 08:12:23 > Subject: Re: failed 430-440 up

Review Request 26969: During VM deployment and while choosing CUSTOM disk offering for data disk, the size of the data disk is not considered for checking resource limit of primary storage.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26969/ --- Review request for cloudstack and Kishan Kavala. Bugs: CLOUDSTACK-7760 http

Re: Review Request 26361: CLOUDSTACK-7660: Enhance system vm template to support baremetal

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26361/ --- (Updated Oct. 21, 2014, 1:02 p.m.) Review request for cloudstack, Frank Zhang a

Re: [PROPOSAL] Remove SNAPSHOT from versioning and keep tags on the release branch

Rohit, I would much prefer something like Nate suggestions, at least when working with cloudstack build from git source is easy to know using the cloudstack version api call and rpm packages name. Rohit, just be sure, what you are suggesting is ,as example, for branch 4.5 until 4.5.0 is GA, the v

Re: [PROPOSAL] Remove SNAPSHOT from versioning and keep tags on the release branch

Unfortunately maven's concept of multi-module projects requires that the sub projects define the version of the parent that they want. So it is scattered throughout all the pom files, but there is a handy maven plugin that can update them all for you. I think the bigger problem is around the os pac

Re: [PROPOSAL] Remove SNAPSHOT from versioning and keep tags on the release branch

Hi, > On 21-Oct-2014, at 9:40 pm, Nate Gordon wrote: > > Unfortunately maven's concept of multi-module projects requires that the > sub projects define the version of the parent that they want. So it is > scattered throughout all the pom files, but there is a handy maven plugin > that can update

Re: commits on 4.5

Hi Daan, Do you know if the check-in protocol for 4.5 (or rather for any branched release) is formally documented on the Wiki somewhere? If it's not, it's probably harder to "enforce" it. Thanks! Mike On Tue, Oct 21, 2014 at 1:21 AM, Daan Hoogland wrote: > David, > > I keep seeing commits pas

Re: Review Request 26871: CLOUDSTACK-7748: Cloudstack version number is missing in system vm template.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26871/#review57604 --- tools/appliance/definitions/systemvmtemplate/configure_systemvm_ser

Re: commits on 4.5

We are well past feature freeze - but I haven't started a hard code freeze; though it is imminent. --David On Tue, Oct 21, 2014 at 12:46 PM, Mike Tutkowski wrote: > Hi Daan, > > Do you know if the check-in protocol for 4.5 (or rather for any branched > release) is formally documented on the Wiki

RE: commits on 4.5

Sorry, I am not aware of the 4.5 release policy, I'll revert my commits on 4.5. > -Original Message- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: Tuesday, October 21, 2014 12:22 AM > To: dev; David Nalley > Subject: commits on 4.5 > > David, > > I keep seeing commits pa

Re: commits on 4.5

So, in the past, feature freeze has been when we branch from master (in this case, 4.5) and then people check directly into 4.5 until the RM has called code freeze (at which point, we started using that -forward concept). Where did we land on that? Once code freeze has passed, do people need to cr

Re: commits on 4.5

I would hold off on that, Edison. We need to make sure the policy is clear (and probably documented) first. On Tue, Oct 21, 2014 at 10:57 AM, Edison Su wrote: > Sorry, I am not aware of the 4.5 release policy, I'll revert my commits on > 4.5. > > > -Original Message- > > From: Daan Hoog

RE: Help in Adding XenServer to CS Management Server

Hi Rajani, The SSVM is up and I can see it green in XenCenter. The systemvm.iso is available in the XenServer host. Below is the snapshot of it. [root@DCM-Xen-69 ~]# ls -al /opt/xensource/packages/iso/ total 160684 drwxr-xr-x 2 root root 4096 Oct 15 10:49 . drwxr-xr-x 5 root root 4096

Build failed in Jenkins: build-4.5 #35

See Changes: [sudison] Revert "fix kvm issue, for windows sever 2008, it will crash without hyperv enlightment featre enabled" [sudison] Revert "There are few cases that mgt server won't reponse agent's pingcommand timely, or in KVM's c

Re: Unreleased 4.4.1 packages on cloudstack.apt-get.eu, why?

well, cheers for that, looks like I am going to use them tonight. :) -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Daan Hoogland" > To: "dev" > Sent: Monday, 20 October, 2014 22:05:05 > Subject: Re: Unreleased 4.4.1 packages on clo

Re: pre-announcement of release 4.4.1

This look really good! On Tue, Oct 21, 2014 at 3:14 AM, Daan Hoogland wrote: > H devs, as the finalisation of the release announcement is taking some > time, here is the sneak preview: > > = = = > > [APACHE CLOUDSTACK LOGO] > > Announcing Apache™ CloudStack™ v4.4.1 > > Mature, easy-to-deploy Ope

Re: Help in Adding XenServer to CS Management Server

Make sure you are using the right systemvm.iso, for this version and for this hypervisor. You won't find scripts if scripts in sytemvm.iso havent been injected onto ssvm You can also login from Xencenter into ssvm and check logs as well. On 21/10/14 10:03 AM, "Ritu Sabharwal" wrote: >Hi Rajani,

Re: commits on 4.5

I wouldn't do that either Edison, that's up to David. I think the practice of making hotfix branches is good in any case. The thing that worries me most is that commits are being entered seperately on both 45 and master instead of merging back. On Tue, Oct 21, 2014 at 7:01 PM, Mike Tutkowski wro

Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

Hi, I want to upgrade a 4.3.1 installation to 4.4.1. Am I still required to add the 4.4.0-6 template before in order for this thing to succeed or has that been solved? Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

yes, i am afraid you are. On Tue, Oct 21, 2014 at 9:15 PM, Nux! wrote: > Hi, > > I want to upgrade a 4.3.1 installation to 4.4.1. > Am I still required to add the 4.4.0-6 template before in order for this > thing to succeed or has that been solved? > > Lucian > > -- > Sent from the Delta quadran

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

So, to clarify: - I need to add "systemvm-kvm-4.4" from http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-kvm.qcow2.bz2 - And then add the same "systemvm-kvm-4.4" (same name? won't cause problems?) from http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.1-7-xen.v

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

you will add the seond one after the db upgrade. the first one is needed during the db upgrade. flakey, i admit. On Tue, Oct 21, 2014 at 9:24 PM, Nux! wrote: > So, to clarify: > - I need to add "systemvm-kvm-4.4" from > http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-kvm.qco

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

Roger that, flakey is ok, as long as we know the exact steps to take. :) -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Daan Hoogland" > To: "dev" > Sent: Tuesday, 21 October, 2014 20:26:09 > Subject: Re: Is the 4.4.0 template still

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

Since we're at it, can anyone confirm the "manual systemvm hotfix" is no longer needed with 4.4.1? https://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.0/upgrade/upgrade-4.3.html#manual-hofix -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Or

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

On Tue, Oct 21, 2014 at 9:32 PM, Nux! wrote: > ual sys that would be once you install the 4.4.1 templates, yes. remind me often we need to upgrade the systemvm upgrade mechs -- Daan

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

I read wrong. didn't think this was needed this way for the 4.4.0 templates, only for the 4.4.1 templates. On Tue, Oct 21, 2014 at 9:35 PM, Daan Hoogland wrote: > On Tue, Oct 21, 2014 at 9:32 PM, Nux! wrote: >> ual sys > > > that would be once you install the 4.4.1 templates, yes. remind me > of

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

Right, so the steps would be: - install 4.4.0-6 systemvm - upgrade management/db - install 4.4.1 systemvm - do the manual db hotfix thing - finally restart the systemvms so they use the 4.4.1 template Does that cover it? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro --

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

it most certainly does On Tue, Oct 21, 2014 at 9:38 PM, Nux! wrote: > Right, so the steps would be: > > - install 4.4.0-6 systemvm > - upgrade management/db > - install 4.4.1 systemvm > - do the manual db hotfix thing > - finally restart the systemvms so they use the 4.4.1 template > > Does that

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

Ok, cheers. I'll start shortly, fingers crossed. :) -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Daan Hoogland" > To: "dev" > Sent: Tuesday, 21 October, 2014 20:39:50 > Subject: Re: Is the 4.4.0 template still necessary for upgrad

Certificate expired

Hi, I just started getting this test-run error message on two of my CloudStack dev boxes today (below). I don't recall sign-signing a certificate, but perhaps I just forgot. Can someone give me the context around this error? Thanks! Results : -

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

Well, hit a small issue: - added 4.4.0 systemvm - OK - upgraded management/db - OK - add 4.4.1 systemvm - FAIL - "Cannot use reserved names for templates" So the names from the 4.4.0 and 4.4.1 systemvm names are identical and conflict. I added the 4.4.1 systemvm as systemvm-kvm-4.4.1. Would this

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

So what I see has happened is as a result of the DB upgrade from 4.3.1 to 4.4.1 the systemvm-kvm-4.4 (4.4.0-6) has been marked of type System, it's not deletable now. Also its ID in the DB is now present as the template to use for ConsoleProxy, SSVM and VR. It's as if the hotfix was performed,

RE: Help in Adding XenServer to CS Management Server

Hi Nitin, I have picked the system vm template from http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/lastStableBuild/ . This Build #132. My XenServer is 5.6 SP2 and CS Mgmt Server is built from master. Please verify is this is the right combination. Thanks & Regards, Ri

Re: Help in Adding XenServer to CS Management Server

I am talking about systemvm.iso and not the systemvm template Systemvm.iso contains all our systemvm (ssvm, cpvm, routervm) agent code(java + some scripts) that gets patched onto the systemvms once they are deployed. Did you build your systemvm.iso recently [1] (mvn clean install -P developer,sy

Re: Help in Adding XenServer to CS Management Server

Sorry got sent accidentally [2] - https://cwiki.apache.org/confluence/display/CLOUDSTACK/SystemVm.iso On 21/10/14 1:45 PM, "Nitin Mehta" wrote: >I am talking about systemvm.iso and not the systemvm template >Systemvm.iso contains all our systemvm (ssvm, cpvm, routervm) agent >code(java + some

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

Well, that didn't go so well. Trying to "hotfix" the 4.4.1 systemvm resulted in successfull SSVM and CP VMs to be restarted, however the VR upgrade went bad: http://pastebin.com/raw.php?i=SB3tYHZc I'll try to downgrade to the 4.4.0 Sys VM and see if that will work. -- Sent from the Delta quadra

RE: Certificate expired

I met the error too. It's caused by file ./server/test/resources/certs/rsa_self_signed.crt which is expired today. I thought we need to replace it with a new one commit 0076307863e9155273d9e4c14282de429388c9e9 Author: Syed Date: Wed Nov 6 15:08:42 2013 -0500 Squashed merge of Ssl Terminat

Re: Certificate expired

Interesting...I just updated master and tried to re-build, but that test failed again. On Tue, Oct 21, 2014 at 4:12 PM, Frank Zhang wrote: > I met the error too. > It's caused by file ./server/test/resources/certs/rsa_self_signed.crt > which is expired today. > I thought we need to replace it wi

RE: Certificate expired

What did you update? You replace the file with you manually built certificate? > -Original Message- > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > Sent: Tuesday, October 21, 2014 3:16 PM > To: dev@cloudstack.apache.org > Subject: Re: Certificate expired > > Interesting...I

Re: Certificate expired

No, sorry...I didn't clarify. I thought you were saying this was all fixed in code, so I updated and tried to re-build the codebase: mvn -P developer,systemvm clean install But it failed on the same test. On Tue, Oct 21, 2014 at 4:17 PM, Frank Zhang wrote: > What did you update? You replace th

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

Hi. Sorry to see this thread late. Upgrading from 4.3.1 to 4.4.1 only require one systemvm template. (The one with -7). Refer to 4.4.1 release notes , it should point to proper urls for sysvm too. Le mardi 21 octobre 2014, Nux! a écrit : > Well, that didn't go so well. Trying to "hotfix" the 4

Review Request 27000: CLOUDSTACK-7762 -[Automation] - Fix test failure for test_02_revert_vm_snapshots in smoke/test_vm_snapshots.py

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27000/ --- Review request for cloudstack, anthony xu and Chandan Purushothama. Bugs: CLOUD

RE: Certificate expired

I made a new certificate, but there are lots of unit cases using different CAs; some of them use correct file; some of them use incorrect file. It takes time to understand what files need to be updated. > -Original Message- > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > Se

Re: Certificate expired

I see - thanks. On Tue, Oct 21, 2014 at 4:36 PM, Frank Zhang wrote: > I made a new certificate, but there are lots of unit cases using different > CAs; some of them use correct file; some of them use incorrect file. > It takes time to understand what files need to be updated. > > > -Original

Re: Review Request 27000: CLOUDSTACK-7762 -[Automation] - Fix test failure for test_02_revert_vm_snapshots in smoke/test_vm_snapshots.py

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27000/#review57694 --- Ship it! Ship It! - Chandan Purushothama On Oct. 21, 2014, 10:34

UUID versus GUID in cluster table

Hi, Just curious...why do we have both a UUID and a GUID field in the cluster table? Thanks, Mike -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud

RE: Certificate expired

I updated three certificated and disabled 4 cases that I cannot figure out the test logic. The patch has been pushed to master; the build is working now. I will send a mail to original author for those 4 disabled cases. > -Original Message- > From: Mike Tutkowski [mailto:mike.tutkow...@so

Re: [PROPOSAL] Move to github PR only during moratorium on commit

Hi Sebastien: So I like the idea of: 1. Us putting up all inbound code for review. 2. Gating that code on a testing pass 3. Having someone else look at it before committing. I don't think that should mean that all code that works gets an immediate pass. I also don't think that we should have n R

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

Thanks for that. I went back to 431, but I'll try one more time to upgrade to 4.4.1 without the 4.4.0 sysvm step. Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Pierre-Luc Dion" > To: dev@cloudstack.apache.org > Sent: Tuesda

Re: Certificate expired

Thanks, Frank! On Tue, Oct 21, 2014 at 5:20 PM, Frank Zhang wrote: > I updated three certificated and disabled 4 cases that I cannot figure out > the test logic. > The patch has been pushed to master; the build is working now. > I will send a mail to original author for those 4 disabled cases. >

Re: Review Request 27000: CLOUDSTACK-7762 -[Automation] - Fix test failure for test_02_revert_vm_snapshots in smoke/test_vm_snapshots.py

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27000/#review57716 --- Ship it! Ship It! - anthony xu On Oct. 21, 2014, 10:34 p.m., san

431 to 441, VR upgrade fails with VR config: execution failed: "/opt/cloud/bin/createipAlias.sh"

Hi, I almost upgraded from 4.3.1 to 4.4.1, everything went smoothly except the VR upgrade (the other sysvms are fine). It will not upgrade, even if I delete it and create another, same story: On the agent I see: 2014-10-22 01:17:17,857 DEBUG [kvm.resource.LibvirtComputingResource] (agentReque

Build failed in Jenkins: build-4.5 #36

See Changes: [anthony.xu] CLOUDSTACK-7761: -- [...truncated 1828 lines...] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.295 sec Running org.apache.cloudstack.region.RegionManage

Re: 431 to 441, VR upgrade fails with VR config: execution failed: "/opt/cloud/bin/createipAlias.sh"

Hi Nux, There is spelling mistake 'i' instead of 'I' in the file name 'createipAlias.sh' Work around is in VR change createIpAlias.sh -> createipAlias.sh Observe the MS log once the VR entered into Running state stop the MS so that VR won't be destroyed. Now go to VR and change the file name. T

Review Request 27017: CLOUDSTACK-6282: Added newly automated tests and also modified some existing tests to remove dependency

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27017/ --- Review request for cloudstack and Santhosh Edukulla. Bugs: CLOUDSTACK-6282

Review Request 27021: Reservations for VMware VMs remain after dynamic scaling

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27021/ --- Review request for cloudstack and Kishan Kavala. Bugs: CLOUDSTACK-7763 http