[jira] [Issue Comment Deleted] (CLOUDSTACK-2589) [Automation] Failed to ssh to LB enabled VM

["Alena Prokharchyk (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alena Prokharchyk updated CLOUDSTACK-2589:
------------------------------------------

    Comment: was deleted

(was: 
Commenting on : "results in the both public port and private port to be saved as public port.". The port saved in firewall_rules table, is a public port. I know its confusing that we show it as a range (default_port_start, default_port_end), but as this table is used by firewall_rules as well (where the range is supported), so keeping it in the DB as a range, is fine.


Private port is saved in load_balancing_rules table.)
    
> [Automation] Failed to ssh to LB enabled VM 
> --------------------------------------------
>
>                 Key: CLOUDSTACK-2589
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2589
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.2.0
>         Environment: Master commit 776921a5f7d7cb944e5cc47766c264480cc9fb9f
> KVM , VM ware and Xen automation runs
>            Reporter: Rayees Namathponnan
>            Assignee: Alena Prokharchyk
>            Priority: Blocker
>             Fix For: 4.2.0
>
>
> Automation test cases 
> /test/integration/smoke/test_network.py
> Steps to reproduce 
> Run BVT test test_network.py:TestLoadBalancingRule
> or 
> Step 1 : Create advance zone, create VM and new Network
> Step 2 : Create LB rule Private port 22, pubic port 2222
> Step 3 : Create Firewall, start port : 2222 and end port : 2222
> Step 4 : login into the VM trough SSH 
> Actual Result 
> Failed to login to the VM 
> While create LB, if you set Private port to 22, its storing as 2222

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira