[
https://issues.apache.org/jira/browse/CLOUDSTACK-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574860#comment-13574860
]
Prachi Damle commented on CLOUDSTACK-1200:
------------------------------------------
The need of storing disk_offering_id in vm_instance arises because cloud-engine
is now relaying the createVM call from UserVmManager to VirtualMachineManager.
This property is needed to send the required disk offerings to
VirtualMachineManager API.
However if we do this refactorig mentioned here:
https://issues.apache.org/jira/browse/CLOUDSTACK-1217
then we dont need the disk_offerin_ig property any more.
So after fixing https://issues.apache.org/jira/browse/CLOUDSTACK-1217, I will
remove the disk_offering_id. Till then we will keep this in the schema.
-------------------------------
The bug mentions that the column is not found in the database. This is a issue
with deployDB and db upgrade step. Assigning to Rohit to take a look.
The issue is 4.1-new-db-schema.sql is not being run. Root cause is that in
create-schema.sql we insert the version to be 4.1 :
INSERT INTO `version` (`version`, `updated`, `step`) VALUES('4.1.0', now(),
'Complete');
So db upgarde does not run the 4.1 script since it finds that the version is
already 4.1.
> Unknown column 'vm_instance.disk_offering_id' in table vm_instance, db
> exception shown in MS log
> ------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1200
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1200
> 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: CentOS 6.3
> 368d5a1ea597c612e050613e13c95687bc0992c2
> Reporter: Rayees Namathponnan
> Assignee: Prachi Damle
> Priority: Blocker
> Fix For: 4.1.0
>
>
> Step 1 : Created new build from 4.1 branch
> Step 2 : Install and configure MS server
> You can see below exception log also in error dialog displayed in UI
> 2013-02-07 16:54:36,464 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
> (consoleproxy-1:null) Skip capacity scan due to there is no Primary Storage
> UPintenance mode
> 2013-02-07 16:54:40,115 ERROR
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Fail to complete the CheckRouterTask!
> com.cloud.utils.exception.CloudRuntimeException: DB Exception on:
> com.mysql.jdbc.JDBC4PreparedStatement@67b9238a: SELECT vm_instance.id,
> vm_instance.name, vm_instance.vnc_password, vm_instance.proxy_id,
> vm_instance.proxy_assign_time, vm_instance.state,
> vm_instance.private_ip_address, vm_instance.instance_name,
> vm_instance.vm_template_id, vm_instance.guest_os_id, vm_instance.host_id,
> vm_instance.last_host_id, vm_instance.pod_id,
> vm_instance.private_mac_address, vm_instance.data_center_id,
> vm_instance.vm_type, vm_instance.ha_enabled, vm_instance.limit_cpu_use,
> vm_instance.update_count, vm_instance.created, vm_instance.removed,
> vm_instance.update_time, vm_instance.domain_id, vm_instance.account_id,
> vm_instance.service_offering_id, vm_instance.reservation_id,
> vm_instance.hypervisor_type, vm_instance.uuid, vm_instance.disk_offering_id,
> domain_router.element_id, domain_router.public_ip_address,
> domain_router.public_mac_address, domain_router.public_netmask,
> domain_router.is_redundant_router, domain_router.priority,
> domain_router.is_priority_bumpup, domain_router.redundant_state,
> domain_router.stop_pending, domain_router.role,
> domain_router.template_version, domain_router.scripts_version,
> domain_router.vpc_id FROM domain_router INNER JOIN vm_instance ON
> domain_router.id=vm_instance.id INNER JOIN router_network_ref ON
> domain_router.id=router_network_ref.router_id WHERE
> vm_instance.type='DomainRouter' AND vm_instance.removed IS NULL AND
> (router_network_ref.guest_type = 'Isolated' )
> at
> com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:412)
> at
> com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:347)
> at
> com.cloud.utils.db.GenericDaoBase.listIncludingRemovedBy(GenericDaoBase.java:899)
> at com.cloud.utils.db.GenericDaoBase.listBy(GenericDaoBase.java:876)
> at com.cloud.utils.db.GenericDaoBase.listBy(GenericDaoBase.java:889)
> at
> com.cloud.vm.dao.DomainRouterDaoImpl.listIsolatedByHostId(DomainRouterDaoImpl.java:213)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at
> com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:37)
> at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> at
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
> at
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl$CheckRouterTask.run(VirtualNetworkApplianceManagerImpl.java:1295)
> in db i cannot see the cloumn vm_instance.disk_offering_id
> mysql> desc vm_instance;
> +---------------------+---------------------+------+-----+---------+-------+
> | Field | Type | Null | Key | Default | Extra |
> +---------------------+---------------------+------+-----+---------+-------+
> | id | bigint(20) unsigned | NO | PRI | NULL | |
> | name | varchar(255) | NO | | NULL | |
> | uuid | varchar(40) | YES | UNI | NULL | |
> | instance_name | varchar(255) | NO | | NULL | |
> | state | varchar(32) | NO | MUL | NULL | |
> | desired_state | varchar(32) | YES | | NULL | |
> | vm_template_id | bigint(20) unsigned | YES | MUL | NULL | |
> | guest_os_id | bigint(20) unsigned | NO | | NULL | |
> | private_mac_address | varchar(17) | YES | | NULL | |
> | private_ip_address | char(40) | YES | | NULL | |
> | pod_id | bigint(20) unsigned | YES | MUL | NULL | |
> | data_center_id | bigint(20) unsigned | NO | MUL | NULL | |
> | host_id | bigint(20) unsigned | YES | MUL | NULL | |
> | last_host_id | bigint(20) unsigned | YES | MUL | NULL | |
> | proxy_id | bigint(20) unsigned | YES | | NULL | |
> | proxy_assign_time | datetime | YES | | NULL | |
> | vnc_password | varchar(255) | NO | | NULL | |
> | ha_enabled | tinyint(1) | NO | | 0 | |
> | limit_cpu_use | tinyint(1) unsigned | NO | | 0 | |
> | update_count | bigint(20) unsigned | NO | MUL | 0 | |
> | update_time | datetime | YES | MUL | NULL | |
> | created | datetime | NO | | NULL | |
> | removed | datetime | YES | MUL | NULL | |
> | type | varchar(32) | NO | MUL | NULL | |
> | vm_type | varchar(32) | NO | | NULL | |
> | account_id | bigint(20) unsigned | NO | MUL | NULL | |
> | domain_id | bigint(20) unsigned | NO | | NULL | |
> | service_offering_id | bigint(20) unsigned | NO | MUL | NULL | |
> | reservation_id | char(40) | YES | | NULL | |
> | hypervisor_type | char(32) | YES | | NULL | |
> +---------------------+---------------------+------+-----+---------+-------+
> 30 rows in set (0.03 sec)
--
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
