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 D851BFDC9 for ; Tue, 26 Mar 2013 10:25:17 +0000 (UTC) Received: (qmail 51043 invoked by uid 500); 26 Mar 2013 10:25:17 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 50984 invoked by uid 500); 26 Mar 2013 10:25:17 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 50967 invoked by uid 500); 26 Mar 2013 10:25:17 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 50942 invoked by uid 99); 26 Mar 2013 10:25:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Mar 2013 10:25:17 +0000 Date: Tue, 26 Mar 2013 10:25:17 +0000 (UTC) From: "Pradeep Soundararajan (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-1694) Issues to start/access Management Server after upgrade from 4.0 to 4.1 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-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613667#comment-13613667 ] Pradeep Soundararajan commented on CLOUDSTACK-1694: --------------------------------------------------- I am unable to reproduce the same with the below steps: 1) wget http://jenkins.cloudstack.org/view/4.0/job/build-4.0-nonoss-rhel63/142/artifact/CloudStack-non-OSS-142.tar.bz2 2) untar it and installed it using ./install.sh 3) cloud-setup-databases cloud:freebsd@localhost --deploy-as=root:freebsd 3) Able to launch MS of 4.0 (cloud-setup-management). 4) Copied the local 4.1 build and installed it using ./install.sh (I have not created the repo manually since install.sh script does everything for me). Right now Install wont show any upgrade option, it will show just Install MS (click Install MS). I have to update the script based on the findings and feedbacks for upgrade. 5) cloudstack-setup-databases cloud:freebsd@localhost --deploy-as=root:freebsd 6) cloudstack-setup-management (it created the below symb links properly) lrwxrwxrwx. 1 root root 44 Mar 26 15:16 server.xml -> /etc/cloudstack/management/server-nonssl.xml lrwxrwxrwx. 1 root root 46 Mar 26 15:16 tomcat6.conf -> /etc/cloudstack/management/tomcat6-nonssl.conf 7) Able to launch MS of 4.1. Hence dropping this defect from blocker. Please let me know if I am missing anything or I have to test and implement anything for this upgrade. Thanks, Pradeep S > Issues to start/access Management Server after upgrade from 4.0 to 4.1 > ---------------------------------------------------------------------- > > Key: CLOUDSTACK-1694 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1694 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Install and Setup, Management Server > Affects Versions: 4.1.0 > Reporter: Sailaja Mada > Assignee: Pradeep Soundararajan > Priority: Critical > Fix For: 4.1.0 > > Attachments: apilog.log, catalina.out, management-server.log, Upgrade-4.0-4.1.rar > > > Setup: Advanced Networking Zone with Xen 6.0.2 host > Steps: > 1. Install and configure 4.0 setup > 2. Create 4.1 repo and update the packages to 4.1 > 3. Tried to start Management server > Issue1 : Failed to start management server as there is no tomcat6.conf file > Resolved: Created a copy of tomcat6-nonssl.conf to tomcat6.conf > Issue2 : Failed to start MS as there is no server.xml > Resolved: Created a copy of server-nonssl.xml to server.xml > Issue3: Failed to start MS as connection to DB failed when DB access is set with password. > Resolved: db.properties file is the newly created file and it has cloud user password as cloud , where as my db has password as the cloud user password. Tried changing it to password and ran cloudstack-setup-encryption. MS failed to start again. I changed it to cleartext. Then Management server started. > Issue4 : DB version is not updated to 4.1. > 2013-03-18 12:18:19,947 INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-1:null) Performing database integrity check > 2013-03-18 12:18:19,988 DEBUG [cloud.upgrade.DatabaseIntegrityChecker] (Timer-1:null) No duplicate hosts with the same local storage found in database > 2013-03-18 12:18:19,995 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-1:null) Checking to see if the database is at a version before it was the version table is created > 2013-03-18 12:18:20,062 INFO [utils.component.ComponentContext] (Timer-1:null) Running SystemIntegrityChecker managementServerNode > 2013-03-18 12:18:20,072 INFO [utils.component.ComponentContext] (Timer-1:null) Running SystemIntegrityChecker premiumDatabaseUpgradeChecker > 2013-03-18 12:18:20,072 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Grabbing lock to check for database upgrade. > 2013-03-18 12:18:20,073 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-1:null) Checking to see if the database is at a version before it was the version table is created > 2013-03-18 12:18:20,081 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) DB version = 4.0.0.20130314045651 Code Version = 4.1.0-SNAPSHOT > 2013-03-18 12:18:20,081 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Database upgrade must be performed from 4.0.0.20130314045651 to 4.1.0-SNAPSHOT > 2013-03-18 12:18:20,085 DEBUG [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Running upgrade Upgrade40to41 to upgrade from 4.0.0-4.1.0 to 4.1.0 > 2013-03-18 12:18:20,104 DEBUG [utils.script.Script] (Timer-1:null) Looking for db/schema-40to410.sql in the classpath > 2013-03-18 12:18:20,131 DEBUG [utils.script.Script] (Timer-1:null) System resource: file:/usr/share/cloudstack-management/setup/db/schema-40to410.sql > 2013-03-18 12:18:20,131 DEBUG [utils.script.Script] (Timer-1:null) Absolute path = /usr/share/cloudstack-management/setup/db/schema-40to410.sql > 2013-03-18 12:18:20,157 DEBUG [utils.db.ScriptRunner] (Timer-1:null) -- Licensed to the Apache Software Foundation (ASF) under one > 2013-03-18 12:18:20,157 DEBUG [utils.db.ScriptRunner] (Timer-1:null) -- or more contributor license agreements. See the NOTICE file > Now Packages got upgraded and Ms started . But > Issue 5: Admin Failed to Access Management Server after upgrade from 4.0 to 4.1. > 2013-03-15 14:57:40,307 INFO [cloud.api.ApiServer] (catalina-exec-2:null) 10.144.6.39 -- GET command=listCapabilities&response=json&sessionkey=iz3R6InbJpcujm59mnfAyVhxFi8%3D&_=1363339696558 401 unable to verify user credentials > 2013-03-15 14:57:52,836 INFO [cloud.api.ApiServer] (catalina-exec-25:null) (userId=2 accountId=2 sessionId=BB2EFE205EB7BD4B18764E2A62FC92B0) 10.144.6.39 -- POST command=login domain=/ > 2013-03-15 14:57:52,858 INFO [cloud.api.ApiServer] (catalina-exec-9:null) 10.144.6.39 -- GET command=listCapabilities&response=json&sessionkey=grCL9c4pqkBoadh5wR9UeGG0DNc%3D&_=1363339709156 432 The given command does not exist or it is not available for user > 2013-03-15 14:57:52,873 INFO [cloud.api.ApiServer] (catalina-exec-15:null) 10.144.6.39 -- GET command=listSwifts&response=json&sessionkey=grCL9c4pqkBoadh5wR9UeGG0DNc%3D&_=1363339709174 432 The given command does not exist or it is not available for user > 2013-03-15 14:58:02,760 INFO [cloud.api.ApiServer] (catalina-exec-5:null) (userId=2 accountId=2 sessionId=42D6696ACE3E2D92A83051F83EC9DEBB) 10.144.6.39 -- POST command=login domain=/ > 2013-03-15 14:58:02,778 INFO [cloud.api.ApiServer] (catalina-exec-8:null) 10.144.6.39 -- GET command=listCapabilities&response=json&sessionkey=Kf8n0aN%2BrFAIccQmIs%2BN6HSGJKY%3D&_=1363339719078 432 The given command does not exist or it is not available for user > 2013-03-15 14:58:02,803 INFO [cloud.api.ApiServer] (catalina-exec-11:null) 10.144.6.39 -- GET command=listSwifts&response=json&sessionkey=Kf8n0aN%2BrFAIccQmIs%2BN6HSGJKY%3D&_=1363339719097 432 The given command does not exist or it is not available for user > 2013-03-15 14:58:35,120 INFO [cloud.api.ApiServer] (catalina-exec-14:null) 10.144.6.39 -- GET command=listCapabilities&response=json&sessionkey=Kf8n0aN%2BrFAIccQmIs%2BN6HSGJKY%3D&_=1363339751394 432 The given command does not exist or it is not available for user > 2013-03-15 14:58:48,637 INFO [cloud.api.ApiServer] (catalina-exec-20:null) (userId=2 accountId=2 sessionId=6D393B5E8AEEA3D4DE35DAED11BEDDD6) 10.144.6.39 -- POST command=login domain=/ > 2013-03-15 14:58:48,719 INFO [cloud.api.ApiServer] (catalina-exec-7:null) 10.144.6.39 -- GET command=listCapabilities&response=json&sessionkey=bWJUWg0w2C5bU3ts7gES43tM30w%3D&_=1363339764994 432 The given command does not exist or it is not available for user > 2013-03-15 14:58:48,778 INFO [cloud.api.ApiServer] (catalina-exec-24:null) 10.144.6.39 -- GET command=listSwifts&response=json&sessionkey=bWJUWg0w2C5bU3ts7gES43tM30w%3D&_=1363339765053 432 The given command does not exist or it is not available for user > Followed below steps at the management server to get the repo of 4.1 ready : > a) yum install httpd [ Webserver] > b) Allo 80/8250 port > iptables -I INPUT -p tcp --dport 8250 -j ACCEPT > iptables -I INPUT -p tcp --dport 80 -j ACCEPT > c) yum install createrepo > d)Download 4.1 packages and run createrepo ./ under this extracted folder where packages exists > e) Copy the packages folder to /var/www/html [cp -R CloudStack-non-OSS-4.1-101-rhel6.3 /var/www/html/] > f) yum update cloud-* > It updated the packages: > apache-cloudstack | 1.3 kB 00:00 > apache-cloudstack/primary | 3.5 kB 00:00 > apache-cloudstack 9/9 > Setting up Update Process > Resolving Dependencies > --> Running transaction check > ---> Package cloud-aws-api.x86_64 0:4.0.0-0.142.el6.4.0.0 will be obsoleted > ---> Package cloud-client.x86_64 0:4.0.0-0.142.el6.4.0.0 will be obsoleted > ---> Package cloud-client-ui.x86_64 0:4.0.0-0.142.el6.4.0.0 will be obsoleted > ---> Package cloud-core.x86_64 0:4.0.0-0.142.el6.4.0.0 will be obsoleted > ---> Package cloud-deps.x86_64 0:4.0.0-0.142.el6.4.0.0 will be obsoleted > ---> Package cloud-python.x86_64 0:4.0.0-0.142.el6.4.0.0 will be obsoleted > ---> Package cloud-scripts.x86_64 0:4.0.0-0.142.el6.4.0.0 will be obsoleted > ---> Package cloud-server.x86_64 0:4.0.0-0.142.el6.4.0.0 will be obsoleted > ---> Package cloud-setup.x86_64 0:4.0.0-0.142.el6.4.0.0 will be obsoleted > ---> Package cloud-utils.x86_64 0:4.0.0-0.142.el6.4.0.0 will be obsoleted > ---> Package cloudstack-awsapi.x86_64 0:4.1.0-SNAPSHOT.el6 will be obsoleting > ---> Package cloudstack-common.x86_64 0:4.1.0-SNAPSHOT.el6 will be obsoleting > ---> Package cloudstack-management.x86_64 0:4.1.0-SNAPSHOT.el6 will be obsoleting > --> Finished Dependency Resolution > Dependencies Resolved > ===================================================================================================================================================================================================== > Package Arch Version Repository Size > ===================================================================================================================================================================================================== > Installing: > cloudstack-awsapi x86_64 4.1.0-SNAPSHOT.el6 apache-cloudstack 60 M > replacing cloud-aws-api.x86_64 4.0.0-0.142.el6.4.0.0 > cloudstack-common x86_64 4.1.0-SNAPSHOT.el6 apache-cloudstack 92 M > replacing cloud-core.x86_64 4.0.0-0.142.el6.4.0.0 > replacing cloud-deps.x86_64 4.0.0-0.142.el6.4.0.0 > replacing cloud-python.x86_64 4.0.0-0.142.el6.4.0.0 > replacing cloud-scripts.x86_64 4.0.0-0.142.el6.4.0.0 > replacing cloud-setup.x86_64 4.0.0-0.142.el6.4.0.0 > replacing cloud-utils.x86_64 4.0.0-0.142.el6.4.0.0 > cloudstack-management x86_64 4.1.0-SNAPSHOT.el6 apache-cloudstack 57 M > replacing cloud-client.x86_64 4.0.0-0.142.el6.4.0.0 > replacing cloud-client-ui.x86_64 4.0.0-0.142.el6.4.0.0 > replacing cloud-server.x86_64 4.0.0-0.142.el6.4.0.0 > Transaction Summary > ===================================================================================================================================================================================================== > Install 3 Package(s) > Total download size: 209 M > Is this ok [y/N]: y > Downloading Packages: > (1/3): cloudstack-awsapi-4.1.0-SNAPSHOT.el6.x86_64.rpm | 60 MB 00:00 > (2/3): cloudstack-common-4.1.0-SNAPSHOT.el6.x86_64.rpm | 92 MB 00:01 > (3/3): cloudstack-management-4.1.0-SNAPSHOT.el6.x86_64.rpm | 57 MB 00:02 > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > Total 44 MB/s | 209 MB 00:04 > Running rpm_check_debug > Running Transaction Test > Transaction Test Succeeded > Running Transaction > Installing : cloudstack-common-4.1.0-SNAPSHOT.el6.x86_64 1/13 > Installing : cloudstack-awsapi-4.1.0-SNAPSHOT.el6.x86_64 2/13 > Installing : cloudstack-management-4.1.0-SNAPSHOT.el6.x86_64 3/13 > Please download vhd-util from http://download.cloud.com.s3.amazonaws.com/tools/vhd-util and put it in > /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/ > Erasing : cloud-client-ui-4.0.0-0.142.el6.4.0.0.x86_64 4/13 > Erasing : cloud-client-4.0.0-0.142.el6.4.0.0.x86_64 5/13 > Stopping cloud-management:[ OK ] > warning: /etc/cloud/management/server.xml saved as /etc/cloud/management/server.xml.rpmsave > warning: /etc/cloud/management/db.properties saved as /etc/cloud/management/db.properties.rpmsave > Erasing : cloud-setup-4.0.0-0.142.el6.4.0.0.x86_64 6/13 > Erasing : cloud-server-4.0.0-0.142.el6.4.0.0.x86_64 7/13 > Erasing : cloud-core-4.0.0-0.142.el6.4.0.0.x86_64 8/13 > Erasing : cloud-aws-api-4.0.0-0.142.el6.4.0.0.x86_64 9/13 > Erasing : cloud-deps-4.0.0-0.142.el6.4.0.0.x86_64 10/13 > Erasing : cloud-utils-4.0.0-0.142.el6.4.0.0.x86_64 11/13 > Erasing : cloud-scripts-4.0.0-0.142.el6.4.0.0.x86_64 12/13 > Erasing : cloud-python-4.0.0-0.142.el6.4.0.0.x86_64 13/13 > Installed products updated. > Verifying : cloudstack-common-4.1.0-SNAPSHOT.el6.x86_64 1/13 > Verifying : cloudstack-management-4.1.0-SNAPSHOT.el6.x86_64 2/13 > Verifying : cloudstack-awsapi-4.1.0-SNAPSHOT.el6.x86_64 3/13 > Verifying : cloud-aws-api-4.0.0-0.142.el6.4.0.0.x86_64 4/13 > Verifying : cloud-python-4.0.0-0.142.el6.4.0.0.x86_64 5/13 > Verifying : cloud-scripts-4.0.0-0.142.el6.4.0.0.x86_64 6/13 > Verifying : cloud-utils-4.0.0-0.142.el6.4.0.0.x86_64 7/13 > Verifying : cloud-deps-4.0.0-0.142.el6.4.0.0.x86_64 8/13 > Verifying : cloud-core-4.0.0-0.142.el6.4.0.0.x86_64 9/13 > Verifying : cloud-client-4.0.0-0.142.el6.4.0.0.x86_64 10/13 > Verifying : cloud-client-ui-4.0.0-0.142.el6.4.0.0.x86_64 11/13 > Verifying : cloud-server-4.0.0-0.142.el6.4.0.0.x86_64 12/13 > Verifying : cloud-setup-4.0.0-0.142.el6.4.0.0.x86_64 13/13 > Installed: > cloudstack-awsapi.x86_64 0:4.1.0-SNAPSHOT.el6 cloudstack-common.x86_64 0:4.1.0-SNAPSHOT.el6 cloudstack-management.x86_64 0:4.1.0-SNAPSHOT.el6 > Replaced: > cloud-aws-api.x86_64 0:4.0.0-0.142.el6.4.0.0 cloud-client.x86_64 0:4.0.0-0.142.el6.4.0.0 cloud-client-ui.x86_64 0:4.0.0-0.142.el6.4.0.0 cloud-core.x86_64 0:4.0.0-0.142.el6.4.0.0 > cloud-deps.x86_64 0:4.0.0-0.142.el6.4.0.0 cloud-python.x86_64 0:4.0.0-0.142.el6.4.0.0 cloud-scripts.x86_64 0:4.0.0-0.142.el6.4.0.0 cloud-server.x86_64 0:4.0.0-0.142.el6.4.0.0 > cloud-setup.x86_64 0:4.0.0-0.142.el6.4.0.0 cloud-utils.x86_64 0:4.0.0-0.142.el6.4.0.0 > Complete! > =================================================== > : -- 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