cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wilder Rodrigues <>
Subject Re: [Blocker/Critical] VR related Issues
Date Tue, 08 Sep 2015 11:35:22 GMT
Hi guys,

Thanks for reporting those issues.

Concerning the following issues…

* Remote Access VPN
* Default INPUT/Forward policies
* Default route not configured on VPC
* site2site VPN

… we already got PRs to be reviewed/tested, but we are lacking response from the community
on those. All the PRs above already got 1 LGTM. Could you reserve some time to review/test
what is categorised as blocker so we can move forward?

I will look into the issue and come
back to you.


On 08 Sep 2015, at 11:41, Koushik Das <<>>

I am also seeing this issue This is
a blocker for regular isolated network as VR is not coming to 'up' state due to ssh failure.

-----Original Message-----
From: Bharat Kumar []
Sent: Thursday, 3 September 2015 15:44
Subject: Re: [Blocker/Critical] VR related Issues


found few more issues related to rvr in isolated networks.
There seems to be a problem with the keepalived config and setting up of default routes when
rvr changes states.

created bugs for these issues.


On 12-Aug-2015, at 10:52 am, Bharat Kumar <<><>>


looks like  there is  one more issue. Conntrackd fails to start in case of rvr enabled isolated
created a bug to track this.


On 11-Aug-2015, at 3:03 pm, Kishan Kavala <<><>>

Below VR related issues currently open. Most of these issues did not exist in 4.5.x and are
related to VR refactor (persistent VR).

Blocker - Remote Access VPN not working

Critical - Default policy for INPUT and FORWARD
chain is ACCEPT in VR filter table (Wilder is working on this) - CS does not honor the default deny
egress policy in isolated network - site2site vpn iptables rules are not
configured on VR - Default route is not configured on
VPC VR  - Monitor service cron job not visible

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message