cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4091) 4.1 fresh install doesn't work in dev environment
Date Wed, 07 Aug 2013 22:56:47 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732881#comment-13732881
] 

ASF subversion and git services commented on CLOUDSTACK-4091:
-------------------------------------------------------------

Commit ae8159b8560181f5935443876862f8b826bc0a31 in branch refs/heads/4.1 from [~vijayendrabvs]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ae8159b ]

CLOUDSTACK-4091: 4.1 fresh install doesn't work in dev environment
Reviewed-by: Alena Prokharchyk
Description:

    Put in upgrade path in DatabaseUpgradeChecker
    to implement db upgrade from 4.1.1 to 4.1.2.

                
> 4.1 fresh install doesn't work in dev environment 
> --------------------------------------------------
>
>                 Key: CLOUDSTACK-4091
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4091
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.1.1
>         Environment: This is a fresh installation of the mgmt server in a dev environment
on top of the latest 4.1 branch.
>            Reporter: Venkata Siva Vijayendra Bhamidipati
>            Assignee: Venkata Siva Vijayendra Bhamidipati
>            Priority: Critical
>             Fix For: 4.1.1
>
>
> The compilation goes through, but the mgmt server fails to come up with the following
error:
> .
> .
> INFO  [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker encryptionSecretKeyChecker
INFO  [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker databaseIntegrityChecker
INFO  [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Grabbing lock to check for database
integrity.
> INFO  [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Performing database integrity
check INFO  [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker managementServerNode
INFO  [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker databaseUpgradeChecker
INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Grabbing lock to check for database
upgrade.
> INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) DB version = 4.0.0 Code Version
= 4.1.2-SNAPSHOT INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Database upgrade
must be performed from 4.0.0 to 4.1.2-SNAPSHOT ERROR [cloud.upgrade.DatabaseUpgradeChecker]
(Timer-2:) The end upgrade version is actually at 4.1.1 but our management server code version
is at 4.1.2-SNAPSHOT ERROR [utils.component.ComponentContext] (Timer-2:) System integrity
check failed. Refuse to startup
> 2013-08-02 09:40:39.356:INFO::Shutdown hook executing
> 2013-08-02 09:40:39.357:INFO::Stopped SelectChannelConnector@0.0.0.0:8080
> 2013-08-02 09:40:39.862:INFO:/client:Closing Spring root WebApplicationContext .
> .
> mysql> select * from db_version;
> ERROR 1146 (42S02): Table 'cloud.db_version' doesn't exist
> mysql> select * from version;
> +----+---------+---------------------+----------+
> | id | version | updated             | step     |
> +----+---------+---------------------+----------+
> |  1 | 4.0.0   | 2013-08-02 09:38:16 | Complete |
> +----+---------+---------------------+----------+
> 1 row in set (0.01 sec)
> mysql>

--
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

Mime
View raw message