cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Makrand <makrandsa...@gmail.com>
Subject Re: [error] Unable to create a deployment for VM
Date Mon, 07 Dec 2015 12:51:53 GMT
Hello,

Important thing is for every action (creation/deletion/snapshot etc etc),
there will be job ID. If you start tracking from job ID (job-2566 in your
current case), you will get picture of what happened during process and
where it failed exactly.

Just check logs around

2015-12-07 11:21:00,815

There is few exceptions, with last one being following. (Seems the problem
with your storage or KVM hypervisor not able to communicate with storage
properly (Check KVM libvert/settings etc). )

2015-12-07 11:21:00,815 WARN  [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(Work-Job-Executor-161:ctx-ae277d5c job-2566/job-2567 ctx-997c4fec)
Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@6dc558b4),
no need to delete from object in store ref table
2015-12-07 11:21:00,815 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Work-Job-Executor-161:ctx-ae277d5c job-2566/job-2567 ctx-997c4fec)
Unable to create Vol[295|vm=249|ROOT]:java.lang.NullPointerException


2015-12-07 11:21:00,815 INFO  [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-161:ctx-ae277d5c job-2566/job-2567 ctx-997c4fec)
Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource
[StoragePool:18] is unreachable: Unable to create
Vol[295|vm=249|ROOT]:java.lang.NullPointerException
        at org.apache.cloudstack.utils.qemu.QemuImg$PreallocationType.getPreallocationType(QemuImg.java:65)
        at com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createPhysicalDiskByQemuImg(LibvirtStorageAdaptor.java:720)
        at com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createPhysicalDisk(LibvirtStorageAdaptor.java:658)
        at com.cloud.hypervisor.kvm.storage.LibvirtStoragePool.createPhysicalDisk(LibvirtStoragePool.java:119)
        at com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createDiskFromTemplate(LibvirtStorageAdaptor.java:918)
        at com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createDiskFromTemplate(KVMStoragePoolManager.java:336)
        at com.cloud.hypervisor.kvm.storage.KVMStorageProcessor.cloneVolumeFromBaseTemplate(KVMStorageProcessor.java:337)
        at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:82)
        at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:53)
        at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1386)
        at com.cloud.agent.Agent.processRequest(Agent.java:503)
        at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
        at com.cloud.utils.nio.Task.run(Task.java:84)
        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)

Makrand

On Mon, Dec 7, 2015 at 5:00 PM, Paez Sanchez Paula Carlota <
paulacarlota.paezsanchez@gemalto.com> wrote:

> Hi,
>
>
>
>
>
> I’m writing to ask for support in an issue I bumped into after being a
> considerable time a daily user of Cloudstack.
>
>
>
> The case is:
>
>
>
> I created a domain, added a cluster with a dedicated host. Everything
> worked fine until I added the first instance to it.
>
> The error:
>
>
>
> Job failed due to exception Unable to create a deployment for
> VM[User|i-36-249-VM]
>
>
>
> The log:
>
>
>
> Attached document.
>
>
>
> Cloudstack version : 4.4.2 [It’s impossible for the moment to upgrade it]
>
>
>
>
>
>
> Many thanks in advance.
>
>
>
>
>
> Paula C. Páez
> ------------------------------
> This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for
> the message if altered, changed or falsified. If you are not the intended
> recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission
> free from viruses, the sender will not be liable for damages caused by a
> transmitted virus.
>



-- 
Makrand

Trust your own instinct. Your mistakes might as well be your own, instead
of someone else’s.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message