The patch is for CLOUDSTACK-2067. I just opened the new bug and committed a
fix to master for it, which should apply to 4.1. CLOUDSTACK-2071.
On Wed, Apr 17, 2013 at 1:10 PM, Chip Childers wrote:
> On Wed, Apr 17, 2013 at 11:59:59AM -0600, Marcus Sorensen wrote:
> > I'm testing the fix for that
On Wed, Apr 17, 2013 at 11:59:59AM -0600, Marcus Sorensen wrote:
> I'm testing the fix for that now.
>
> Also, this fix revealed an upstream bug in the management server. There is
> a path in advanceStart that can allow it to complete and return a null
> object without having successfully started
I'm testing the fix for that now.
Also, this fix revealed an upstream bug in the management server. There is
a path in advanceStart that can allow it to complete and return a null
object without having successfully started the VM. The caller of this
method (the orch service) doesn't care about the
431 should be fixed already few months ago.
Sent from my Windows Phone
From: Marcus Sorensen<mailto:shadow...@gmail.com>
Sent: 3/23/2013 3:13 PM
To: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>
Subject: Re: [ACS41] Status
1006 I jus
Please wait until the fix for CLOUDSTACK-1795 is in. The fix will finalize
on how Spring to fully work with legacy CloudStack AOP semantics (@DB
interception/@ActionEvent interception).
Out-of-box Spring AOP offering uses proxy mode that can not fully support
the semantics we used in legacy CloudS
1006 I just closed, it ended up being a duplicate of a bug recently fixed.
431 references old stuff that doesn't seem to say much any more (or I
can't reach), but I believe it's about trying to bring up a zone when
you have a bunch of hosts. The management server can't handle all of
the agents con
On 23 March 2013 00:19, Chip Childers wrote:
> Hi all,
>
> I'm not going to cut the RC today, due to the outstanding bugs that we
> are still working on.
>
> Let's keep pushing to get things wrapped up. I've been trying to get
> review requests *with my name on them* and / or "Patch Request" emai
