Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Fri, 14 Nov 2014 08:39:35 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12744624.1411982372000.498355.1415954375700@Atlassian.JIRA>
In-Reply-To: <JIRA.12744624.1411982372000@Atlassian.JIRA>
References: <JIRA.12744624.1411982372000@Atlassian.JIRA>
 <JIRA.12744624.1411982372502@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-7642)
 [Upgrade]java.lang.ClassNotFoundException after upgrading to 4.5 from 4.3.0
 with Xenserver HV.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Commit a782495c68c2b27dff2d659ec87a0ec90c9ceb02 in cloudstack's branch refs/heads/4.5 from [~devdeep]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a782495 ]

CLOUDSTACK-7642. Class not found exception after upgrading from 4.3 to 4.5 on a
XenServer hypervisor setup. The resource path has changed for xenserver resources
in 4.5. On an upgraded setup the db entries in host table for the resource path
needs to be updated. Made a fix in the upgrade script.


> [Upgrade]java.lang.ClassNotFoundException after upgrading to 4.5 from 4.3.0 with Xenserver HV.
> ----------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7642
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7642
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Upgrade
>    Affects Versions: 4.5.0
>         Environment: upgrade from 4.3.0 to 4.5 using Xen server 6.2 
>            Reporter: manasaveloori
>            Assignee: Devdeep Singh
>            Priority: Blocker
>             Fix For: 4.5.0
>
>         Attachments: management-server.rar, mysqldump4.5.rar, mysqldumpBeforeUp.rar
>
>
> 1. Deployed 4.3.0 CS with 1zone,1 pod,1cluster,2 Xen 6.2 HVs using 4.3.0 build.
> 2. Registered the 4.5 template as "systemvm-xenserver-4.5"
> 3. Upgraded to 4.5 and started the MS.
> Observation:
> Observed the following exception in MS logs .Hosts went into disconnected stated.
> 2014-09-29 13:45:26,849 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] (ClusteredAgentManager Timer:ctx-7b268e53) Loading directly connected host 1(Rack1Pod1Host29)
> 2014-09-29 13:45:26,851 WARN  [c.c.r.DiscovererBase] (ClusteredAgentManager Timer:ctx-7b268e53) Unable to find class com.cloud.hypervisor.xen.resource.XenServer620Resource
> java.lang.ClassNotFoundException: com.cloud.hypervisor.xen.resource.XenServer620Resource
>         at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1484)
>         at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1329)
>         at java.lang.Class.forName0(Native Method)
>         at java.lang.Class.forName(Class.java:186)
>         at com.cloud.resource.DiscovererBase.getResource(DiscovererBase.java:89)
>         at com.cloud.resource.DiscovererBase.reloadResource(DiscovererBase.java:150)
>         at com.cloud.agent.manager.AgentManagerImpl.loadDirectlyConnectedHost(AgentManagerImpl.java:680)
>         at com.cloud.agent.manager.ClusteredAgentManagerImpl.scanDirectAgentToLoad(ClusteredAgentManagerImpl.java:219)
>         at com.cloud.agent.manager.ClusteredAgentManagerImpl.runDirectAgentScanTimerTask(ClusteredAgentManagerImpl.java:185)
>         at com.cloud.agent.manager.ClusteredAgentManagerImpl.access$100(ClusteredAgentManagerImpl.java:99)
>         at com.cloud.agent.manager.ClusteredAgentManagerImpl$DirectAgentScanTimerTask.runInContext(ClusteredAgentManagerImpl.java:235)
>         at org.apache.cloudstack.managed.context.ManagedContextTimerTask$1.runInContext(ManagedContextTimerTask.java:30)
>         at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
>         at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
>         at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
>         at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
>         at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
>         at org.apache.cloudstack.managed.context.ManagedContextTimerTask.run(ManagedContextTimerTask.java:27)
>         at java.util.TimerThread.mainLoop(Timer.java:555)
>         at java.util.TimerThread.run(Timer.java:505)
> 2014-09-29 13:45:26,852 WARN  [c.c.a.m.AgentManagerImpl] (ClusteredAgentManager Timer:ctx-7b268e53) Unable to load the resource: 1
> 2014-09-29 13:45:26,853 DEBUG [c.c.h.Status] (ClusteredAgentManager Timer:ctx-7b268e53) Transition:[Resource state = Enabled, Agent event = AgentDisconnected, Host id = 1, name = Rack1Pod1Host29]
> Attaching the dumps and logs.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)