Whoops, I actually replied to this twice but I sent it to myself instead of the
list lol. I actually ended up fixing this:
2013-08-01 15:11:35,151 DEBUG [xen.resource.CitrixResourceBase]
(AgentTaskPool-3:null) Management network is on
pif=f6ca9e23-77a1-37e1-b5e8-744e7a612945
2013-08-01 15:11:35,161 WARN [xen.resource.CitrixResourceBase]
(AgentTaskPool-3:null) Unable to find storage network cloud-stor1 for host
10.10.2.11
2013-08-01 15:11:35,161 WARN [xen.resource.CitrixResourceBase]
(AgentTaskPool-3:null) Unable to get host information for 10.10.2.11
java.lang.IllegalArgumentException: Unable to find storage network cloud-stor1
for host 10.10.2.11
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getHostInfo(CitrixResourceBase.java:4364)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.initialize(CitrixResourceBase.java:4496)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.initialize(XenServer56Resource.java:323)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1907)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:2084)
at
com.cloud.agent.manager.AgentManagerImpl$SimulateStartTask.run(AgentManagerImpl.java:1156)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
That was the error I was getting every time it tried to connect to a XenServer
host.
There was an entry in my host_details table called storage.network.device1and
storage.network.device2 that with values of cloud-stor1 and cloud-stor2. I
don't remember ever setting these networks up, and they don't actually exist on
my XenServer hosts at all. I removed the entries from my database and the
XenServer hosts connected just fine.
This is an environment that has been running since 2.2.1 according to my
version table. I am not sure that if maybe an older version of CS was creating
these these storage network tags automatically? I checked another deployment
that was deployed on 3.0.2 with XenServer 5.6SP2 and it did not have these
entries in the database, and I've been deploying XenServer the same way for a
long time with CloudStack. Was quite weird.
On Aug 1, 2013, at 4:54 PM, Chiradeep Vittal <[email protected]>
wrote:
> Logs?
>
> On 8/1/13 12:53 PM, "John Skinner" <[email protected]> wrote:
>
>> Hello all,
>>
>> Just upgraded my mixed KVM/XenServer environment form 3.0.2 to 4.1. All
>> of my KVM hosts seem happy, but all of my XenServer (5.6SP2) hosts show
>> as disconnected and are not coming back. Has anyone experienced this?
>>
>>
>>
>>
>>
>
