I encountered the reboot in DevCloud2 as well ( http://markmail.org/message/6j6i2wjpknx3vrnz). I hope this can be fixed in the next RC (although not a blocker, I am not sure if it is a DevCloud only issue) I also noticed that the number of VR (CLOUDSTACK-6031) is reported as zero, although if you click through you see the VR. I'm not sure it is a blocker though (the listRouters API returns an empty list if you don't provide listAll=true).
On 2/5/14 10:43 AM, "Animesh Chaturvedi" <animesh.chaturv...@citrix.com> wrote: >Folks need more feedback on this RC besides the one from Daan, Geoff, >Paul. > >Animesh > >> -----Original Message----- >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] >> Sent: Monday, February 03, 2014 2:59 PM >> To: dev@cloudstack.apache.org >> Subject: [VOTE] Apache CloudStack 4.3.0 (third round) >> >> >> Hi All, >> >> I've created a 4.3.0 release, with the following artifacts up for a >>vote: >> >> Git Branch and Commit SH: >> https://git-wip- >> us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3 >> >> Commit: 8f63c2cf9c463373d774cb563e63fc56828e1418 >> >> List of changes: >> <Release notes are still in progress in a different repo, so providing >>links >> here for now> New Features in 4.3: >> https://issues.apache.org/jira/issues/?filter=12325248 >> Improvement in 4.3: >>https://issues.apache.org/jira/issues/?filter=12325249 >> Issues fixed in 4.3 >>https://issues.apache.org/jira/issues/?filter=12326161 >> Known Issues in 4.3: >>https://issues.apache.org/jira/issues/?filter=12326162 >> >> >> >> Source release (checksums and signatures are available at the same >> location): >> https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/ >> >> PGP release keys (signed using 94BE0D7C): >> https://dist.apache.org/repos/dist/release/cloudstack/KEYS >> >> Testing instructions are here: >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+pro >> cedure >> >> Vote will be open for 3 working days (72 hours) and close on Thursday >>2/6 at >> 3:00 PM PST >> >> For sanity in tallying the vote, can PMC members please be sure to >>indicate >> "(binding)" with their vote? >> >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >
