Re: [VOTE] Release Apache CloudStack CloudMonkey 5.3.0 (round #3)

Hi Lucian, Thanks for the logs and reporting the bug. I think it’s fixed now, can you check. > On 01-Nov-2014, at 3:19 am, Nux! wrote: > > Yes, the same happens with commit 300c as well as with your latest (at this > time) d835341e9feec63695a112f092289c8ec7ac972a. > > (testing) 🐵 > deploy virt

Review Request 27464: Remove private key from listSslCerts

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27464/ --- Review request for cloudstack and Will Stevens. Repository: cloudstack-git De

Re: [VOTE] Release Apache CloudStack CloudMonkey 5.3.0 (round #3)

Rohit, cloudstack-cloudmonkey-eae1973 works fine, thanks for fixing it. +1 from me again One more thing, less important; how could I clear the cache, sometimes it looks like a bit aggressive? For example if I just create a couple of VMs and then want to destroy them, if I do destroy virtualmach

Build failed in Jenkins: cloudstack-4.4-maven-build #483

See Changes: [Daan Hoogland] CLOUDSTACK-7526: Fix missing localization on 'add' button -- [...truncated 1326 lines...] [INFO] Using 'UTF-8' encoding to copy filtered resources. [IN

Re: [ACS442] merge request

On Fri, Oct 31, 2014 at 5:04 AM, Pierre-Luc Dion wrote: > b04cc750652642e8e2593128c7c0f5de3ef6b0d7 yes -- Daan

release artifact 4.4.1 faulty. How to resolve?

People, It seems the uploaded artifacts on the release repo of apache does not contain the commit-id of the voted release. I don't know if this can be remedied. I think we should pull it, right? can we replace it by artifacts that do contain the right version? Or should we have a new version? tha

Re: release artifact 4.4.1 faulty. How to resolve?

+1 new version with fixed systemvms :-) -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Daan Hoogland" > To: "dev" , priv...@cloudstack.apache.org > Sent: Saturday, 1 November, 2014 19:12:38 > Subject: release artifact 4.4.1 faulty. H

Re: release artifact 4.4.1 faulty. How to resolve?

Nux, What is broken with systemvm ? So far the only thing I see as problem with 4.4.1 is the manual db update for the missing column. *Pierre-Luc DION* Architecte de Solution Cloud | Cloud Solutions Architect t 855.652.5683 *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts 4

Re: release artifact 4.4.1 faulty. How to resolve?

Pierre, It's this (does not manifest in all cases) https://issues.apache.org/jira/browse/CLOUDSTACK-7781 -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Pierre-Luc Dion" > To: dev@cloudstack.apache.org > Sent: Saturday, 1 November,

Re: release artifact 4.4.1 faulty. How to resolve?

-private We are talking about whats in: https://dist.apache.org/repos/dist/release/cloudstack/releases/4.4.1/ ? If so, I am not sure how we arrive at the fact that the release artifacts aren't what we voted on. I looked at the commit log for the part of the tree and found [1]. I also checked it ou

Re: release artifact 4.4.1 faulty. How to resolve?

I am talking about a mismatch between the commit-id that the tag 4.4..1 points to and the artifact that was uploaded. I think they are functionally the same but the internal version is different. The artifact is 4.4.1-SNAPSHOT hence probably the root of the release branch and the commit is the tip