+0 On a basic zone deployment I seem to be having issues accessing the console proxy.
>From what I can work out this has something to do with the iptables on the hypervisor for security groups. Flushing the iptables on the hypervisor running the console vm fixes the issue but breaks all the security groups. Can anybody else confirm if they experience a similar issue? I did two clean deployments happened both times. Everything else seemed to work fine. On 15 October 2014 12:13, Wido den Hollander <w...@widodh.nl> wrote: > +1 > > Based on the commits that have happened my old tests are still valid. > > Wido > > On 10/14/2014 11:23 PM, Daan Hoogland wrote: > > Hi All, > > > > As all open blocking issues were reported fixed today, I've created a > 4.4.1 > > 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.4-RC20141014T2316 > > Commit: 8db506b536f3139250d33df571c98c1c3fa83650 > > > > List of changes: > > > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/ > > > > Source release (checksums and signatures are available at the same > > location): > > https://dist.apache.org/repos/dist/dev/cloudstack/4.4.1/ > > > > PGP release keys (signed using 4096R/AA4736F3): > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS > > > > Vote will be open for 72 hours. > > > > 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) > > may for(tun/c)e be with us, > > >
