Harikrishna Patnala created CLOUDSTACK-8888:
-----------------------------------------------
Summary: Xenserver 6.0.2 host stuck in disconnected state after
upgrade to master
Key: CLOUDSTACK-8888
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8888
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server, XenServer
Reporter: Harikrishna Patnala
Assignee: Harikrishna Patnala
Fix For: 4.6.0
hosts running XenServer 6.0.2 are stuck in disconnected state after CS was
upgraded to master. I have upgraded the XenServer host to v6.2 but still show
in disconnected state.
It seems Xenserver602resource class is removed but did not handle the existing
xenserver 6.0.2 hosts.
found the below exception during reloading resource.
2015-09-21 15:29:19,423 WARN [c.c.r.DiscovererBase] (ClusteredAgentManager
Timer:ctx-d6747f5a) Unable to find class
com.cloud.hypervisor.xenserver.resource.XenServer602Resource
java.lang.ClassNotFoundException:
com.cloud.hypervisor.xenserver.resource.XenServer602Resource
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
at
org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:401)
at
org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:363)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:190)
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:697)
at
com.cloud.agent.manager.ClusteredAgentManagerImpl.scanDirectAgentToLoad(ClusteredAgentManagerImpl.java:220)
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:236)
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)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
