[
https://issues.apache.org/jira/browse/CLOUDSTACK-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Sorensen updated CLOUDSTACK-1648:
----------------------------------------
Attachment: 0000-non-persistent-storage-pools.patch
This might not be the final fix, I need to do a lot of testing on it, but I
want to see if it fixes the issue. It accomplishes two things: It makes storage
pool definitions non-persistent, and it looks for storage pools by path and
allows an existing pool with the path you want to use to be redefined with the
correct UUID/name.
I do think ultimately that this might be a configuration mismatch between
agent.properties file and cloudstack database, possibly due to redeploying on a
pre-existing host or config, but I'm not sure. Please test this against 4.1 and
let me know. Also try stopping/starting the agent if you get connected and see
if it does anything strange.
> Unable to add KVM host
> -----------------------
>
> Key: CLOUDSTACK-1648
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1648
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM
> Affects Versions: 4.0.0, 4.1.0
> Reporter: Harikrishna Patnala
> Assignee: Rajesh Battala
> Priority: Blocker
> Fix For: 4.0.2
>
> Attachments: 0000-non-persistent-storage-pools.patch
>
>
> Trying to add a kvm host in basic zone.
> Failed after time out occured.
> Checked the agent log in KVM host, seems like conflict occurring with storage
> pool.
> Tried removing the storage pool and re-installing the cloudstack agent.
> Even then failing on the same error.
> Here is the cloudstack agent log in kvm:
> 2013-03-12 09:26:46,159 DEBUG [kvm.resource.LibvirtComputingResource]
> (Agent-Handler-1:null) cpus=2, speed=2992, ram=3846610944, dom0ram=384661094
> 2013-03-12 09:26:46,163 DEBUG [cloud.resource.ServerResourceBase]
> (Agent-Handler-1:null) Parameters for private nic: 10.147.28.22 -
> bc:30:5b:a0:a7:7f-255.255.255.0
> 2013-03-12 09:26:46,163 DEBUG [cloud.resource.ServerResourceBase]
> (Agent-Handler-1:null) Parameters for storage nic: 10.147.28.22 -
> bc:30:5b:a0:a7:7f-255.255.255.0
> 2013-03-12 09:26:46,163 DEBUG [cloud.resource.ServerResourceBase]
> (Agent-Handler-1:null) Parameters for pubic nic: 10.147.28.22 -
> bc:30:5b:a0:a7:7f-255.255.255.0
> 2013-03-12 09:26:46,163 DEBUG [kvm.resource.LibvirtComputingResource]
> (Agent-Handler-1:null) Executing:
> /usr/share/cloudstack-common/scripts/vm/hypervisor/versions.sh
> 2013-03-12 09:26:46,173 DEBUG [kvm.resource.LibvirtComputingResource]
> (Agent-Handler-1:null) Execution is successful.
> 2013-03-12 09:26:46,181 DEBUG [kvm.storage.LibvirtStorageAdaptor]
> (Agent-Handler-1:null) <pool type='dir'>
> <name>7a0e2394-dbc7-497d-bfb9-98609ca2e36f</name>
> <uuid>7a0e2394-dbc7-497d-bfb9-98609ca2e36f</uuid>
> <target>
> <path>/var/lib/libvirt/images/</path>
> </target>
> </pool>
> 2013-03-12 09:26:46,183 ERROR [kvm.storage.LibvirtStorageAdaptor]
> (Agent-Handler-1:null) org.libvirt.LibvirtException: operation failed:
> Storage source conflict with pool: '97b3188f-32c6-4637-9bc6-084fa1bbaa14'
> 2013-03-12 09:26:46,184 WARN [utils.nio.Task] (Agent-Handler-1:null) Caught
> the following exception but pushing on
> java.lang.NullPointerException
> at
> com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:462)
> at
> com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:103)
> at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.initialize(LibvirtComputingResource.java:3528)
> at com.cloud.agent.Agent.sendStartup(Agent.java:320)
> at com.cloud.agent.Agent$ServerHandler.doTask(Agent.java:871)
> at com.cloud.utils.nio.Task.run(Task.java:83)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
--
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
