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

Marcus Sorensen commented on CLOUDSTACK-1505:
---------------------------------------------

I didn't realize that a fresh 4.1 install would need to upgrade schema from 4.0 
to 4.1. I thought the schema should be correct from the start, which seemed 
like a bug.

In the scenario I mentioned (reinstall), it doesn't seem to run the update. I'm 
not sure if this is related to some .properties file that is already there, or 
the management server failing to deploy the update or only partially deploying 
it before the mgmt server got restarted. But now that I know that we deploy a 
4.0 schema and intentionally update it, I can maybe look at the pieces that 
trigger the update if I can find them.
                
> Unknown column 'domain.region_id' in 'field list'
> -------------------------------------------------
>
>                 Key: CLOUDSTACK-1505
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1505
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server
>    Affects Versions: 4.1.0
>         Environment: Management server running on CentOS 6.3
>            Reporter: Marcus Sorensen
>            Assignee: Marcus Sorensen
>            Priority: Critical
>             Fix For: 4.1.0
>
>
> I deploy a management server and database. Then I stop management server, 
> drop database, and then attempt to reinstall. I run:
> cloudstack-setup-databases cloud:password@localhost --deploy-as root
> cloudstack-setup-management
> as I also did during initial successful install. Only this time, I cannot log 
> in as Admin user. The UI does nothing when I attempt to login, and management 
> server says:
> 2013-03-04 16:30:18,950 ERROR [cloud.api.ApiServlet] (catalina-exec-14:null) 
> unknown exception writing api response
> com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
> com.mysql.jdbc.JDBC4PreparedStatement@18f7d92f: SELECT domain.id, 
> domain.parent, domain.name, domain.owner, domain.path, domain.level, 
> domain.removed, domain.child_count, domain.next_child_seq, domain.state, 
> domain.network_domain, domain.uuid, domain.region_id FROM domain WHERE 
> domain.path = _binary'/'  AND domain.removed IS NULL  ORDER BY RAND() LIMIT 1
> Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown 
> column 'domain.region_id' in 'field list'
> Indeed, there is no mention of region_id in the sql deployment, and perhaps 
> whatever injects this into the schema doesn't like a reinstall. This could be 
> hard on devs and people testing out cloudstack.

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

Reply via email to