[
https://issues.apache.org/jira/browse/CLOUDSTACK-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sheng Yang updated CLOUDSTACK-3939:
-----------------------------------
Priority: Critical (was: Blocker)
Fix Version/s: (was: 4.2.0)
Move out of 4.2. It's not a blocker for 4.2.
> [Automation]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
> Assignee: Sheng Yang
> Priority: Critical
> 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
