Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3694C10FD1 for ; Wed, 14 Aug 2013 06:30:54 +0000 (UTC) Received: (qmail 57987 invoked by uid 500); 14 Aug 2013 06:30:52 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 57907 invoked by uid 500); 14 Aug 2013 06:30:52 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 57878 invoked by uid 500); 14 Aug 2013 06:30:52 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 57850 invoked by uid 99); 14 Aug 2013 06:30:51 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Aug 2013 06:30:51 +0000 Date: Wed, 14 Aug 2013 06:30:51 +0000 (UTC) From: "Abhinav Roy (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-4300) [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739287#comment-13739287 ] Abhinav Roy commented on CLOUDSTACK-4300: ----------------------------------------- re-opening the bug as we need more clarity on the upgrade procedure > [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade > ------------------------------------------------------------------------ > > Key: CLOUDSTACK-4300 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4300 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: KVM, SystemVM, Upgrade > Affects Versions: 4.2.0 > Environment: Host : KVM [CentOS 6.1] > MS : CentOS 6.1 > upgrade from 2.2.14 to 4.2 > Reporter: Abhinav Roy > Priority: Blocker > Fix For: 4.2.0 > > Attachments: CS-4300.zip > > > Steps : > ================ > 1. Deploy a CS 2.2.14 advanced zone setup with KVM host. > 2. do some operations like create vm, snapshots, templates, domain, accounts etc > 3. upgrade to 4.2 > Expected behaviour : > =============== > Upgrade should go fine and new system vms should come up > Observed behaviour : > ============== > Upgrade went fine but system vms don't come up, they stay in the starting state. > Attaching management server logs, catalina logs, agent logs and DB dumps -- 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