Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Fri, 3 Jan 2014 07:33:54 +0000 (UTC)
From: "manasaveloori (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12687137.1388734384698.36746.1388734434460@arcas>
In-Reply-To: <JIRA.12687137.1388734384698@arcas>
References: <JIRA.12687137.1388734384698@arcas>
Subject: [jira] [Created] (CLOUDSTACK-5751) Default template is not  ready
  with status "no route to host" after upgrading from 2.2.16 to 4.3
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

manasaveloori created CLOUDSTACK-5751:
-----------------------------------------

             Summary: 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
            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)