cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yugandhar Yetham <yugandhar.yet...@gmail.com>
Subject Re: Failed to create volume when attaching it to VM
Date Sun, 27 Oct 2013 03:08:57 GMT
Hi Sanjay,

As you said that, I created one disk offering with name of "own-disk" with
storage type is local. Now this volume storing on the host where the VMs
are running.
But, I am not sure how to configure the existed zone to use local storage.

Kindly let me know.

-----
Thanks,
Yugandhar Yetham



On Sun, Oct 27, 2013 at 12:18 AM, Sanjay Tripathi <
sanjay.tripathi@citrix.com> wrote:

> Can you verify that disk offering used to create the volume is of "local"
> storage type.
> Also, check if your zone is configured to use local storage.
>
> --Sanjay
>
> > -----Original Message-----
> > From: Yugandhar Yetham [mailto:yugandhar.yetham@gmail.com]
> > Sent: Saturday, October 26, 2013 6:39 PM
> > To: users@cloudstack.apache.org
> > Subject: Failed to create volume when attaching it to VM
> >
> > Hi Users,
> >
> >
> > I am using local storage for guest VMs.
> >
> > I have created a data volume "DATA-1001" but couldn't able to attach it
> to
> > VM. Please check the below log file and let me soloution if i made a
> mistake
> > in configuration.
> >
> > WARN  [cloud.storage.StorageManagerImpl] (Job-Executor-4:job-85) Unable
> > to find storage poll when create volume DATA-1001 ERROR
> > [cloud.async.AsyncJobManagerImpl] (Job-Executor-4:job-85) Unexpected
> > exception while executing
> > org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> > com.cloud.utils.exception.CloudRuntimeException: Failed to create volume
> > when attaching it to VM: ubuntuvm1001
> >     at
> > com.cloud.vm.UserVmManagerImpl.attachVolumeToVM(UserVmManagerI
> > mpl.java:939)
> >     at
> > com.cloud.utils.component.ComponentInstantiationPostProcessor$Intercep
> > torDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> >     at
> > org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execut
> > e(AttachVolumeCmd.java:122)
> >     at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
> >     at
> > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:4
> > 37)
> >     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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.jav
> > a:1146)
> >     at
> > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.ja
> > va:615)
> >     at java.lang.Thread.run(Thread.java:679)
> > INFO  [cloud.ha.HighAvailabilityManagerImpl] (HA-4:) checking health of
> > usage server
> >
> >
> > Thanks in Advance
> >
> > ----
> > Regards,
> > Yugandhar Yetham
>

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