Michael Dickey created CLOUDSTACK-2610:
------------------------------------------
Summary: Unable to add host due to missing setiptables plugin
Key: CLOUDSTACK-2610
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2610
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.0.2
Environment: CentOS 6.2 (64-bit) installed from RPM packages
Reporter: Michael Dickey
After upgrade from 4.0.1 to 4.0.2 I am unable to add hosts back into my
cluster. I keep getting an error about a missing setIptables plugin:
{noformat}
INFO [xen.discoverer.XcpServerDiscoverer] (AgentTaskPool-3:) Host: xen3
connected with hypervisor type: XenServer. Checking CIDR...
INFO [agent.manager.DirectAgentAttache] (AgentTaskPool-3:) StartupAnswer
received 10 Interval = 60
INFO [xen.resource.CitrixResourceBase] (DirectAgent-5:) Host 10.0.2.13
OpaqueRef:16671632-3d13-fded-3729-7e675c3ab790: Host 10.0.2.13 is already setup.
WARN [xen.resource.CitrixResourceBase] (DirectAgent-5:) callHostPlugin failed
for cmd: setIptables with args due to The requested plugin could not be found.
WARN [xen.resource.CitrixResourceBase] (DirectAgent-5:) Unable to setup
com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for cmd:
setIptables with args due to The requested plugin could not be found.
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:3745)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.setIptables(CitrixResourceBase.java:3757)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:4528)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:485)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
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)
WARN [xen.discoverer.XcpServerDiscoverer] (AgentTaskPool-3:) Unable to setup
agent 10 due to callHostPlugin failed for cmd: setIptables with args due to
The requested plugin could not be found.
WARN [agent.manager.AgentManagerImpl] (AgentTaskPool-3:) Monitor
XcpServerDiscoverer$$EnhancerByCGLIB$$350a7d8b says there is an error in the
connect process for 10 due to Reinitialize agent after setup.
INFO [agent.manager.AgentManagerImpl] (AgentTaskPool-3:) Host 10 is
disconnecting with event AgentDisconnected
WARN [cloud.resource.ResourceManagerImpl] (AgentTaskPool-3:) Unable to connect
due to
com.cloud.exception.ConnectionException: Reinitialize agent after setup.
at
com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:651)
at
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:605)
at
com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1505)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1631)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1668)
at
com.cloud.agent.manager.AgentManagerImpl$SimulateStartTask.run(AgentManagerImpl.java:1200)
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)
{noformat}
--
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
