Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of animesh.chaturvedi@citrix.com
 designates 66.165.176.63 as permitted sender)
From: Animesh Chaturvedi <animesh.chaturvedi@citrix.com>
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Subject: RE: [ACS 4.3] RC update
Thread-Topic: [ACS 4.3] RC update
Thread-Index: Ac8L13kjY0h8jLAEREaxPtAr0a/ObwCu4dRwAhdiBfA=
Date: Tue, 21 Jan 2014 21:41:28 +0000
Message-ID: <C3637609BC1C0D40A2AC70F4760C7A2D264C28@SJCPEX01CL02.citrite.net>
References: <C3637609BC1C0D40A2AC70F4760C7A2D252E81@SJCPEX01CL02.citrite.net>
 <C3637609BC1C0D40A2AC70F4760C7A2D258DBF@SJCPEX01CL02.citrite.net>
In-Reply-To: <C3637609BC1C0D40A2AC70F4760C7A2D258DBF@SJCPEX01CL02.citrite.net>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Folks

I don't see any outstanding blockers, the automation results were also publ=
ished and seemed satisfactory.  I will process with building RC later today=
  I will also pull in few issues that were under discussion in security mai=
ling list but later were identified as hardening issues (unencrypted passwo=
rds) and did not require to go through security process.=20


Thanks
Animesh

-----Original Message-----
From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]=20
Sent: Friday, January 10, 2014 10:08 PM
To: dev@cloudstack.apache.org
Subject: RE: [ACS 4.3] RC update

Folks

Today is the scheduled RC date for ACS 4.3 We are very close with just a fe=
w lingering issues below.


| Jayapal Reddy        | CLOUDSTACK-5848 : [Upgrade3.0.6-4.3]"Unable to par=
se VLAN tag" message when network associated with SRX external firewall dev=
ice is rebooted.                                                           =
  |
| edison su            | CLOUDSTACK-5831 : As regular user , when trying to=
 take a snapshot , snapshot succeeds but user is presented with "The given =
command does not exist or it is not available for user" message.           =
  |
| Unassigned           | CLOUDSTACK-5743 : Download ROOT Volume when the VM=
 is in stopped state is failing with "Forbidden You don't have permission t=
o access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ on this server=
" |
| Likitha Shetty       | CLOUDSTACK-5707 : Hitting multiple exceptions when=
 the Vsphere client is upgraded to 5.5 from 5.1                            =
                                                                           =
  |
| Daan Hoogland        | CLOUDSTACK-5502 : [Automation] createVlanIpRange A=
PI failing, if you pass VLAN                                               =
                                                                           =
  |
| Marcus Sorensen      | CLOUDSTACK-5432 : [Automation] Libvtd getting cras=
hed and agent going to alert start                                         =
                                                                           =
  |
| Sateesh Chodapuneedi | CLOUDSTACK-5408 : [Automation] Failed to deploy vm=
 in vmware environment with error "due to java.io.IOException: Cannot run p=
rogram "mount": java.io.IOException: error=3D12, Cannot allocate memory"   =
    |
| Wei Zhou             | CLOUDSTACK-5144 : [Automation]: Basic Zone Securit=
y Groups - SSH to VM is allowed even when there is no ingress rule defined =
for the security group                                                     =
  |


If you have not played with 4.3 yet please take it for a spin and call out =
any critical issues, I plan to build an RC early next week.=20

Thanks
Animesh

-----Original Message-----
From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]=20
Sent: Tuesday, January 07, 2014 10:51 AM
To: dev@cloudstack.apache.org
Subject: [ACS 4.3] RC update

Folks

Happy new year everyone. I hope you all had a good recharging time off duri=
ng holiday. I want to bring our attention and focus to getting the 4.3 rele=
ase out the door. While our scheduled RC date is this Friday 1/10 but we st=
ill have many open blocker and critical. Please review your backlog of issu=
es and bring them to resolution ASAP and provide a "Due Date" in the bug.  =
We need to absolutely make sure upgrades are working. If you encounter upgr=
ade issue please file them as blockers. I will escalate all current upgrade=
 issues to blocker.

For the most recent release status please visit the 4.3 Release Dashboard [=
1].  I am following up on individual issues directly in JIRA so do watch JI=
RA emails

[1] http://s.apache.org/dFk

Thanks
Animesh