cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-8947) Load Balancer not working with Isolated Networks
Date Wed, 14 Oct 2015 16:33:08 GMT


ASF subversion and git services commented on CLOUDSTACK-8947:

Commit 2ce5a0c964eb660b0f799e1419e9285c200f09e1 in cloudstack's branch refs/heads/master from
[;h=2ce5a0c ]

Merge pull request #931 from ekholabs/fix/loadbalancer

CLOUDSTACK-8947 - Load Balancer not working with Isolated NetworksThis PR fixes the Load Balance
feature by adding iptables rules for the public IP and port of the LB.

In order to cover the changes, I improved and executed the smoke/ In addition,
I also executed many other tests to make sure the main network/VM functionalities are working
as expected.

Test report will follow.

* pr/931:
  CLOUDSTACK-8947 - Do not rely on the machine hostname to verify the test
  CLOUDSTACK-8947 - Fail fast!
  CLOUDSTACK-8947 - Adding some logging to better understand whay is happening with the Processes
  CLOUDSTACK-8947 - Adding some logging to better understand what's happening with the rules
  CLOUDSTACK-8947 - Configure the firewall when the load balancer is setup
  CLOUDSTACK-8947 - Avoid multiple entries in the FW_EGRESS_RULES table
  CLOUDSTACK-8947 - Open the input chain to IP when loadbalancer is configured
  CLOUDSTACK-8947 - FW_EGRESS should be added only to filter table

Signed-off-by: Remi Bergsma <>

> Load Balancer not working with Isolated Networks
> ------------------------------------------------
>                 Key: CLOUDSTACK-8947
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Virtual Router
>    Affects Versions: 4.6.0
>            Reporter: Wilder Rodrigues
>            Assignee: Wilder Rodrigues
>            Priority: Blocker
>             Fix For: 4.6.0
> 1. acquire IP in an isolated network
> 2. go to ipaddress -> configuration -> firewall 
> 3. add firewall exception for port 22
> 4. then add LB rule for port 22 to a user VM
> 5. try sshing to the new acquired ip(in step 1) --- ssh fails

This message was sent by Atlassian JIRA

View raw message