Hi Martin,

here are my 2 cents:
we do not upgrade XenServer in our CS installation at all. What we do is to 
move all VMs from one host, eject it from the pool and delete it from CS. After 
that we are doing a fresh installation of XenServer, create a new pool and add 
this pool as new cluster to CS. Then we move VMs via live migration from the 
old cluster to the new one so we end up in the next free XenServer in the old 
pool to eject it and so on.

Mit freundlichen Grüßen / With kind regards,

Swen


-----Ursprüngliche Nachricht-----
Von: Dag Sonstebo [mailto:[email protected]] 
Gesendet: Donnerstag, 2. Februar 2017 15:15
An: [email protected]
Betreff: Re: Issues upgrading to XenServer 7

Hi Martin

Check 
http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.6/hypervisor/xenserver.html#upgrading-xenserver-versions


Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 02/02/2017, 13:09, "Martin Emrich" <[email protected]> wrote:

    Hi!,
    
    After getting the upgrade to 4.9.2.0 on my test cloud going, I decided to 
upgrade the hosts from XenServer 6.5SP1 to XenServer 7. I followed the process 
like I did many times with upgrades form 6.0 to 6.2 or to 6.5.
    Normally, Cloudstack "reinstalled" the integration scripts under /opt/cloud 
after upgrading a XenServer, I usually can watch it In the logs while it copies 
scripts and stuff to the XenServers.
    
    But this time, they do not appear, and the host stays in the Alert state.
    
    In the log, I see:
    
    2017-02-02 14:07:07,431 DEBUG [c.c.h.Status] (AgentTaskPool-6:ctx-3c41c4cd) 
(logid:47da929b) Transition:[Resource state = Enabled, Agent event = 
AgentDisconnected, Host id = 2, name = cdsdev-xen5]
    2017-02-02 14:07:07,434 WARN  [c.c.r.ResourceManagerImpl] 
(AgentTaskPool-5:ctx-f768a3d8) (logid:aefd7fd0) Unable to connect due to
    com.cloud.exception.ConnectionException: Reinitialize agent after setup.
            at 
com.cloud.hypervisor.xenserver.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:627)
            at 
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:564)
            at 
com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1518)
            at 
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1902)
            at 
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:2035)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
            at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:606)
            at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
            at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
            at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
            at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
            at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
            at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
            at com.sun.proxy.$Proxy161.createHostAndAgent(Unknown Source)
            at 
com.cloud.agent.manager.AgentManagerImpl$SimulateStartTask.runInContext(AgentManagerImpl.java:1135)
            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 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
            at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
            at java.lang.Thread.run(Thread.java:745)
    
    How can I motivate CloudStack to install the agent/scripts on the 
XenServers? Or can I do it manually?
    
    Thanks,
    
    Martin
    
    


[email protected]
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
  
 



- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, 
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet. 

This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient (or have received this e-mail in error) 
please notify 
the sender immediately and destroy this e-mail.  
Any unauthorized copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden. 


Reply via email to