[
https://issues.apache.org/jira/browse/CLOUDSTACK-5751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edison su resolved CLOUDSTACK-5751.
-----------------------------------
Resolution: Invalid
Exactly as you said, ssvm can't ping its own gateway, usually, it means public
network setup has problem.
> Default template is not ready with status "no route to host" after
> upgrading from 2.2.16 to 4.3
> -------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5751
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5751
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Upgrade
> Affects Versions: 4.3.0
> Environment: upgraded from 2.2.16->4.3
> Reporter: manasaveloori
> Assignee: edison su
> Priority: Critical
> Fix For: 4.3.0
>
> Attachments: management-server.log, mysqldump2216.dmp,
> mysqldump4.3.dmp
>
>
> Steps:
> 1. Deploy CS 2.2.16 .
> 2. Deploy the instances using the default template.
> 3. Upgrade the CS to 4.3
> Observation:
> Observed that the default template is not in ready state with status "No
> route to host"
> Attaching the Db dumps and Ms logs
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
