Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 31 Jul 2013 08:13:48 +0000 (UTC)
From: "Girish Shilamkar (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12660624.1375177922796.142879.1375258428591@arcas>
In-Reply-To: <JIRA.12660624.1375177922796@arcas>
References: <JIRA.12660624.1375177922796@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-3939) Rebooting router results in
 ssh to vm failing with "No route to host" error.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725005#comment-13725005 ] 

Girish Shilamkar commented on CLOUDSTACK-3939:
----------------------------------------------

As router is in running state, the PF rule should apply, no ? I will  increase the sleep time even further and check.
                
> Rebooting router results in ssh to vm failing with "No route to host" error.
> ----------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3939
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3939
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API, Automation
>    Affects Versions: 4.2.0
>         Environment: Vmware
>            Reporter: Girish Shilamkar
>            Priority: Blocker
>         Attachments: logs.tgz
>
>
> Steps to reproduce:
> 1. Create a vm
> 2. Associate a public IP with this vm
> 3. Open firewall for this IP
> 4. Create a PF rule for this vm with this public IP
> 5. Reboot the router for the account
> 6. Try to ssh with public IP, results in error "No router to host"
> If above steps are repeated without rebooting the router, ssh succeeds. Probably the PF rule does not work after rebooting the router.
> Only tested with VMware, not sure about other hypervisors.

--
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