[VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Ritu Sabharwal]

Hi Sateesh, Koushik,

I am setting up Vmware Cluster with CS (master) and seeing errors. ilya was 
helping me for this setup and figured out this error.

The System VMs(Secondary Stogare VM and Console Proxy VM) are not coming up 
properly. The system vms are reconfiguring and destroying again and again in 
cycle.

I have used Vmware Vsphere 5.1 SDK for building CS.

The error logs give this error:

2014-09-16 16:11:01,619 WARN  [c.c.h.v.r.VmwareResource] 
(DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd: StartCommand) 
StartCommand failed due to Exception: java.lang.NullPointerException
Message: null

java.lang.NullPointerException
at 
com.cloud.hypervisor.vmware.resource.VmwareResource.postDiskConfigBeforeStart(VmwareResource.java:2094)
at 
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:1685)
at 
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:448)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:294)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
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:744)

Please help to resolve this issue.

Thanks & Regards,
Ritu S.

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[ilya musayev]

++ Likitha Shetty

Ritu,

Please confirm that you've are running latest/synced master branch?

I've noticed a commit by Likitha that may be relevant:

https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=8bb4022f3729154f85036c4a7f55e2de783e4909

Regards
ilya

On 9/16/14, 4:22 PM, Ritu Sabharwal wrote:


Hi Sateesh, Koushik,

I am setting up Vmware Cluster with CS (master) and seeing errors. 
ilya was helping me for this setup and figured out this error.


The System VMs(Secondary Stogare VM and Console Proxy VM) are not 
coming up properly. The system vms are reconfiguring and destroying 
again and again in cycle.


I have used Vmware Vsphere 5.1 SDK for building CS.

The error logs give this error:

2014-09-16 16:11:01,619 WARN  [c.c.h.v.r.VmwareResource] 
(DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd: 
StartCommand) StartCommand failed due to Exception: 
java.lang.NullPointerException


Message: null

java.lang.NullPointerException

at 
com.cloud.hypervisor.vmware.resource.VmwareResource.postDiskConfigBeforeStart(VmwareResource.java:2094)


at 
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:1685)


at 
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:448)


at 
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:294)


at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)


at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)


at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)


at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)


at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)


at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)


at java.util.concurrent.FutureTask.run(FutureTask.java:262)

at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)


at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)


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:744)

Please help to resolve this issue.

Thanks & Regards,

Ritu S.

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[ilya musayev]

++ Mike as per commit

Repository: cloudstack
Updated Branches:
  refs/heads/master d68e13fcb -> 0879ab812


CLOUDSTACK-6170 (VMware root-disk support for managed storage)



On 9/16/14, 4:22 PM, Ritu Sabharwal wrote:


Hi Sateesh, Koushik,

I am setting up Vmware Cluster with CS (master) and seeing errors. 
ilya was helping me for this setup and figured out this error.


The System VMs(Secondary Stogare VM and Console Proxy VM) are not 
coming up properly. The system vms are reconfiguring and destroying 
again and again in cycle.


I have used Vmware Vsphere 5.1 SDK for building CS.

The error logs give this error:

2014-09-16 16:11:01,619 WARN  [c.c.h.v.r.VmwareResource] 
(DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd: 
StartCommand) StartCommand failed due to Exception: 
java.lang.NullPointerException


Message: null

java.lang.NullPointerException

at 
com.cloud.hypervisor.vmware.resource.VmwareResource.postDiskConfigBeforeStart(VmwareResource.java:2094)


at 
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:1685)


at 
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:448)


at 
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:294)


at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)


at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)


at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)


at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)


at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)


at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)


at java.util.concurrent.FutureTask.run(FutureTask.java:262)

at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)


at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)


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:744)

Please help to resolve this issue.

Thanks & Regards,

Ritu S.

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

Can you tell us what commit SHA you are running under?

I just updated master and line 2094 in VmwareResource is the following:

String[] diskChain = diskInfo.getDiskChain();

The only candidate for a NullPointerException there is diskInfo; however,
the previous line would have caught this as it looks like this:

assert (diskInfo != null);

That being the case, I'm curious what commit SHA you saw this on?

Thanks!

On Tue, Sep 16, 2014 at 5:22 PM, Ritu Sabharwal 
wrote:

> Hi Sateesh, Koushik,
>
> I am setting up Vmware Cluster with CS (master) and seeing errors. ilya
> was helping me for this setup and figured out this error.
>
> The System VMs(Secondary Stogare VM and Console Proxy VM) are not coming
> up properly. The system vms are reconfiguring and destroying again and
> again in cycle.
>
> I have used Vmware Vsphere 5.1 SDK for building CS.
>
> The error logs give this error:
>
> 2014-09-16 16:11:01,619 WARN  [c.c.h.v.r.VmwareResource]
> (DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd: StartCommand)
> StartCommand failed due to Exception: java.lang.NullPointerException
> Message: null
>
> java.lang.NullPointerException
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.postDiskConfigBeforeStart(VmwareResource.java:2094)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:1685)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:448)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:294)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> 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:744)
>
> Please help to resolve this issue.
>
> Thanks & Regards,
> Ritu S.
>
>


-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
*™*

RE: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Ritu Sabharwal]

Hi Mike,

I updated the master just now and tried the setup. I see the same error on same 
line number.

Thanks & Regards,
Ritu S.

-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] 
Sent: Tuesday, September 16, 2014 8:32 PM
To: dev@cloudstack.apache.org
Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with 
Vmware setup with CS server

Can you tell us what commit SHA you are running under?

I just updated master and line 2094 in VmwareResource is the following:

String[] diskChain = diskInfo.getDiskChain();

The only candidate for a NullPointerException there is diskInfo; however, the 
previous line would have caught this as it looks like this:

assert (diskInfo != null);

That being the case, I'm curious what commit SHA you saw this on?

Thanks!

On Tue, Sep 16, 2014 at 5:22 PM, Ritu Sabharwal 
wrote:

> Hi Sateesh, Koushik,
>
> I am setting up Vmware Cluster with CS (master) and seeing errors. 
> ilya was helping me for this setup and figured out this error.
>
> The System VMs(Secondary Stogare VM and Console Proxy VM) are not 
> coming up properly. The system vms are reconfiguring and destroying 
> again and again in cycle.
>
> I have used Vmware Vsphere 5.1 SDK for building CS.
>
> The error logs give this error:
>
> 2014-09-16 16:11:01,619 WARN  [c.c.h.v.r.VmwareResource] 
> (DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd: 
> StartCommand) StartCommand failed due to Exception: 
> java.lang.NullPointerException
> Message: null
>
> java.lang.NullPointerException
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.postDiskConfigBeforeStart(VmwareResource.java:2094)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:1685)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:448)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:294)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> 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:744)
>
> Please help to resolve this issue.
>
> Thanks & Regards,
> Ritu S.
>
>


--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
<http://solidfire.com/solution/overview/?video=play>*™*

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Marcus]

Aren't asserts ignored by default? I think we had an issue with asserts in
the past, and I believe at the time the default config had asserts disabled.


On Wed, Sep 17, 2014 at 1:35 PM, Ritu Sabharwal 
wrote:

> Hi Mike,
>
> I updated the master just now and tried the setup. I see the same error on
> same line number.
>
> Thanks & Regards,
> Ritu S.
>
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Tuesday, September 16, 2014 8:32 PM
> To: dev@cloudstack.apache.org
> Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs
> with Vmware setup with CS server
>
> Can you tell us what commit SHA you are running under?
>
> I just updated master and line 2094 in VmwareResource is the following:
>
> String[] diskChain = diskInfo.getDiskChain();
>
> The only candidate for a NullPointerException there is diskInfo; however,
> the previous line would have caught this as it looks like this:
>
> assert (diskInfo != null);
>
> That being the case, I'm curious what commit SHA you saw this on?
>
> Thanks!
>
> On Tue, Sep 16, 2014 at 5:22 PM, Ritu Sabharwal 
> wrote:
>
> > Hi Sateesh, Koushik,
> >
> > I am setting up Vmware Cluster with CS (master) and seeing errors.
> > ilya was helping me for this setup and figured out this error.
> >
> > The System VMs(Secondary Stogare VM and Console Proxy VM) are not
> > coming up properly. The system vms are reconfiguring and destroying
> > again and again in cycle.
> >
> > I have used Vmware Vsphere 5.1 SDK for building CS.
> >
> > The error logs give this error:
> >
> > 2014-09-16 16:11:01,619 WARN  [c.c.h.v.r.VmwareResource]
> > (DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd:
> > StartCommand) StartCommand failed due to Exception:
> > java.lang.NullPointerException
> > Message: null
> >
> > java.lang.NullPointerException
> > at
> >
> com.cloud.hypervisor.vmware.resource.VmwareResource.postDiskConfigBeforeStart(VmwareResource.java:2094)
> > at
> >
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:1685)
> > at
> >
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:448)
> > at
> >
> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:294)
> > at
> >
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> > at
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> > at
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> > at
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> > at
> >
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> > at
> > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> > at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> > at
> >
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> > at
> >
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> > 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:744)
> >
> > Please help to resolve this issue.
> >
> > Thanks & Regards,
> > Ritu S.
> >
> >
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> <http://solidfire.com/solution/overview/?video=play>*™*
>

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

You're right, Marcus. Now that I think about it, asserts are ignored by
default.

On Wed, Sep 17, 2014 at 1:59 PM, Marcus  wrote:

> Aren't asserts ignored by default? I think we had an issue with asserts in
> the past, and I believe at the time the default config had asserts
> disabled.
>
>
> On Wed, Sep 17, 2014 at 1:35 PM, Ritu Sabharwal 
> wrote:
>
> > Hi Mike,
> >
> > I updated the master just now and tried the setup. I see the same error
> on
> > same line number.
> >
> > Thanks & Regards,
> > Ritu S.
> >
> > -Original Message-
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > Sent: Tuesday, September 16, 2014 8:32 PM
> > To: dev@cloudstack.apache.org
> > Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
> > Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs
> > with Vmware setup with CS server
> >
> > Can you tell us what commit SHA you are running under?
> >
> > I just updated master and line 2094 in VmwareResource is the following:
> >
> > String[] diskChain = diskInfo.getDiskChain();
> >
> > The only candidate for a NullPointerException there is diskInfo; however,
> > the previous line would have caught this as it looks like this:
> >
> > assert (diskInfo != null);
> >
> > That being the case, I'm curious what commit SHA you saw this on?
> >
> > Thanks!
> >
> > On Tue, Sep 16, 2014 at 5:22 PM, Ritu Sabharwal 
> > wrote:
> >
> > > Hi Sateesh, Koushik,
> > >
> > > I am setting up Vmware Cluster with CS (master) and seeing errors.
> > > ilya was helping me for this setup and figured out this error.
> > >
> > > The System VMs(Secondary Stogare VM and Console Proxy VM) are not
> > > coming up properly. The system vms are reconfiguring and destroying
> > > again and again in cycle.
> > >
> > > I have used Vmware Vsphere 5.1 SDK for building CS.
> > >
> > > The error logs give this error:
> > >
> > > 2014-09-16 16:11:01,619 WARN  [c.c.h.v.r.VmwareResource]
> > > (DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd:
> > > StartCommand) StartCommand failed due to Exception:
> > > java.lang.NullPointerException
> > > Message: null
> > >
> > > java.lang.NullPointerException
> > > at
> > >
> >
> com.cloud.hypervisor.vmware.resource.VmwareResource.postDiskConfigBeforeStart(VmwareResource.java:2094)
> > > at
> > >
> >
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:1685)
> > > at
> > >
> >
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:448)
> > > at
> > >
> >
> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:294)
> > > at
> > >
> >
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> > > at
> > >
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> > > at
> > >
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> > > at
> > >
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> > > at
> > >
> >
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> > > at
> > > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> > > at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> > > at
> > >
> >
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> > > at
> > >
> >
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> > > 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:744)
> > >
> > > Please help to resolve this issue.
> > >
> > > Thanks & Regards,
> > > Ritu S.
> > >
> > >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the cloud
> > <http://solidfire.com/solution/overview/?video=play>*™*
> >
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
<http://solidfire.com/solution/overview/?video=play>*™*

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

I can set up a VMware cluster hopefully later tonight and see if I can
reproduce this.

Off hand I'm not sure why the "managed" logic would be causing this, though.

In your situation, "managed" should be false and the "standard" logic
should run.

Is this where I can get the latest system template for VMware?

http://jenkins.buildacloud.org/job/build-systemvm64-master/

I see an OVA and a VMDK. Which one do I use for seeding secondary storage
for VMware (it's been a while since I've used VMware a system template)?

Thanks!

On Wed, Sep 17, 2014 at 2:53 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> You're right, Marcus. Now that I think about it, asserts are ignored by
> default.
>
> On Wed, Sep 17, 2014 at 1:59 PM, Marcus  wrote:
>
>> Aren't asserts ignored by default? I think we had an issue with asserts in
>> the past, and I believe at the time the default config had asserts
>> disabled.
>>
>>
>> On Wed, Sep 17, 2014 at 1:35 PM, Ritu Sabharwal 
>> wrote:
>>
>> > Hi Mike,
>> >
>> > I updated the master just now and tried the setup. I see the same error
>> on
>> > same line number.
>> >
>> > Thanks & Regards,
>> > Ritu S.
>> >
>> > -Original Message-
>> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> > Sent: Tuesday, September 16, 2014 8:32 PM
>> > To: dev@cloudstack.apache.org
>> > Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
>> > Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs
>> > with Vmware setup with CS server
>> >
>> > Can you tell us what commit SHA you are running under?
>> >
>> > I just updated master and line 2094 in VmwareResource is the following:
>> >
>> > String[] diskChain = diskInfo.getDiskChain();
>> >
>> > The only candidate for a NullPointerException there is diskInfo;
>> however,
>> > the previous line would have caught this as it looks like this:
>> >
>> > assert (diskInfo != null);
>> >
>> > That being the case, I'm curious what commit SHA you saw this on?
>> >
>> > Thanks!
>> >
>> > On Tue, Sep 16, 2014 at 5:22 PM, Ritu Sabharwal 
>> > wrote:
>> >
>> > > Hi Sateesh, Koushik,
>> > >
>> > > I am setting up Vmware Cluster with CS (master) and seeing errors.
>> > > ilya was helping me for this setup and figured out this error.
>> > >
>> > > The System VMs(Secondary Stogare VM and Console Proxy VM) are not
>> > > coming up properly. The system vms are reconfiguring and destroying
>> > > again and again in cycle.
>> > >
>> > > I have used Vmware Vsphere 5.1 SDK for building CS.
>> > >
>> > > The error logs give this error:
>> > >
>> > > 2014-09-16 16:11:01,619 WARN  [c.c.h.v.r.VmwareResource]
>> > > (DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd:
>> > > StartCommand) StartCommand failed due to Exception:
>> > > java.lang.NullPointerException
>> > > Message: null
>> > >
>> > > java.lang.NullPointerException
>> > > at
>> > >
>> >
>> com.cloud.hypervisor.vmware.resource.VmwareResource.postDiskConfigBeforeStart(VmwareResource.java:2094)
>> > > at
>> > >
>> >
>> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:1685)
>> > > at
>> > >
>> >
>> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:448)
>> > > at
>> > >
>> >
>> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:294)
>> > > at
>> > >
>> >
>> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
>> > > at
>> > >
>> >
>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
>> > > at
>> > >
>> >
>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
>> > > at
>> > >
>> >
>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
>> > > at
>> > >
>

RE: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Ritu Sabharwal]

Hi Mike,

Sure, it will help to see if you can reproduce the error.

I used the system vm template :  
http://cloudstack.apt-get.eu/systemvm/systemvm64template-2014-01-14-master-vmware.ova
 but http://jenkins.buildacloud.org/job/build-systemvm64-master/  is latest and 
OVA is to be used.


Thanks & Regards,
Ritu S.

-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] 
Sent: Wednesday, September 17, 2014 2:17 PM
To: dev@cloudstack.apache.org
Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with 
Vmware setup with CS server

I can set up a VMware cluster hopefully later tonight and see if I can 
reproduce this.

Off hand I'm not sure why the "managed" logic would be causing this, though.

In your situation, "managed" should be false and the "standard" logic should 
run.

Is this where I can get the latest system template for VMware?

http://jenkins.buildacloud.org/job/build-systemvm64-master/

I see an OVA and a VMDK. Which one do I use for seeding secondary storage for 
VMware (it's been a while since I've used VMware a system template)?

Thanks!

On Wed, Sep 17, 2014 at 2:53 PM, Mike Tutkowski < mike.tutkow...@solidfire.com> 
wrote:

> You're right, Marcus. Now that I think about it, asserts are ignored 
> by default.
>
> On Wed, Sep 17, 2014 at 1:59 PM, Marcus  wrote:
>
>> Aren't asserts ignored by default? I think we had an issue with 
>> asserts in the past, and I believe at the time the default config had 
>> asserts disabled.
>>
>>
>> On Wed, Sep 17, 2014 at 1:35 PM, Ritu Sabharwal 
>> 
>> wrote:
>>
>> > Hi Mike,
>> >
>> > I updated the master just now and tried the setup. I see the same 
>> > error
>> on
>> > same line number.
>> >
>> > Thanks & Regards,
>> > Ritu S.
>> >
>> > -Original Message-
>> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> > Sent: Tuesday, September 16, 2014 8:32 PM
>> > To: dev@cloudstack.apache.org
>> > Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
>> > Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System 
>> > VMs with Vmware setup with CS server
>> >
>> > Can you tell us what commit SHA you are running under?
>> >
>> > I just updated master and line 2094 in VmwareResource is the following:
>> >
>> > String[] diskChain = diskInfo.getDiskChain();
>> >
>> > The only candidate for a NullPointerException there is diskInfo;
>> however,
>> > the previous line would have caught this as it looks like this:
>> >
>> > assert (diskInfo != null);
>> >
>> > That being the case, I'm curious what commit SHA you saw this on?
>> >
>> > Thanks!
>> >
>> > On Tue, Sep 16, 2014 at 5:22 PM, Ritu Sabharwal 
>> > 
>> > wrote:
>> >
>> > > Hi Sateesh, Koushik,
>> > >
>> > > I am setting up Vmware Cluster with CS (master) and seeing errors.
>> > > ilya was helping me for this setup and figured out this error.
>> > >
>> > > The System VMs(Secondary Stogare VM and Console Proxy VM) are not 
>> > > coming up properly. The system vms are reconfiguring and 
>> > > destroying again and again in cycle.
>> > >
>> > > I have used Vmware Vsphere 5.1 SDK for building CS.
>> > >
>> > > The error logs give this error:
>> > >
>> > > 2014-09-16 16:11:01,619 WARN  [c.c.h.v.r.VmwareResource] 
>> > > (DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd:
>> > > StartCommand) StartCommand failed due to Exception:
>> > > java.lang.NullPointerException
>> > > Message: null
>> > >
>> > > java.lang.NullPointerException
>> > > at
>> > >
>> >
>> com.cloud.hypervisor.vmware.resource.VmwareResource.postDiskConfigBef
>> oreStart(VmwareResource.java:2094)
>> > > at
>> > >
>> >
>> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareRes
>> ource.java:1685)
>> > > at
>> > >
>> >
>> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(Vm
>> wareResource.java:448)
>> > > at
>> > >
>> >
>> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAg
>> entAttache.java:294)
>&

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

Thanks!

I needed to hold off on building the env and running this test until today
(issue in the lab), but I should be able to set up this config after my
next meeting is over.

On Wed, Sep 17, 2014 at 3:40 PM, Ritu Sabharwal 
wrote:

> Hi Mike,
>
> Sure, it will help to see if you can reproduce the error.
>
> I used the system vm template :
> http://cloudstack.apt-get.eu/systemvm/systemvm64template-2014-01-14-master-vmware.ova
> but http://jenkins.buildacloud.org/job/build-systemvm64-master/  is
> latest and OVA is to be used.
>
>
> Thanks & Regards,
> Ritu S.
>
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Wednesday, September 17, 2014 2:17 PM
> To: dev@cloudstack.apache.org
> Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs
> with Vmware setup with CS server
>
> I can set up a VMware cluster hopefully later tonight and see if I can
> reproduce this.
>
> Off hand I'm not sure why the "managed" logic would be causing this,
> though.
>
> In your situation, "managed" should be false and the "standard" logic
> should run.
>
> Is this where I can get the latest system template for VMware?
>
> http://jenkins.buildacloud.org/job/build-systemvm64-master/
>
> I see an OVA and a VMDK. Which one do I use for seeding secondary storage
> for VMware (it's been a while since I've used VMware a system template)?
>
> Thanks!
>
> On Wed, Sep 17, 2014 at 2:53 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
> > You're right, Marcus. Now that I think about it, asserts are ignored
> > by default.
> >
> > On Wed, Sep 17, 2014 at 1:59 PM, Marcus  wrote:
> >
> >> Aren't asserts ignored by default? I think we had an issue with
> >> asserts in the past, and I believe at the time the default config had
> >> asserts disabled.
> >>
> >>
> >> On Wed, Sep 17, 2014 at 1:35 PM, Ritu Sabharwal
> >> 
> >> wrote:
> >>
> >> > Hi Mike,
> >> >
> >> > I updated the master just now and tried the setup. I see the same
> >> > error
> >> on
> >> > same line number.
> >> >
> >> > Thanks & Regards,
> >> > Ritu S.
> >> >
> >> > -Original Message-
> >> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> >> > Sent: Tuesday, September 16, 2014 8:32 PM
> >> > To: dev@cloudstack.apache.org
> >> > Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
> >> > Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System
> >> > VMs with Vmware setup with CS server
> >> >
> >> > Can you tell us what commit SHA you are running under?
> >> >
> >> > I just updated master and line 2094 in VmwareResource is the
> following:
> >> >
> >> > String[] diskChain = diskInfo.getDiskChain();
> >> >
> >> > The only candidate for a NullPointerException there is diskInfo;
> >> however,
> >> > the previous line would have caught this as it looks like this:
> >> >
> >> > assert (diskInfo != null);
> >> >
> >> > That being the case, I'm curious what commit SHA you saw this on?
> >> >
> >> > Thanks!
> >> >
> >> > On Tue, Sep 16, 2014 at 5:22 PM, Ritu Sabharwal
> >> > 
> >> > wrote:
> >> >
> >> > > Hi Sateesh, Koushik,
> >> > >
> >> > > I am setting up Vmware Cluster with CS (master) and seeing errors.
> >> > > ilya was helping me for this setup and figured out this error.
> >> > >
> >> > > The System VMs(Secondary Stogare VM and Console Proxy VM) are not
> >> > > coming up properly. The system vms are reconfiguring and
> >> > > destroying again and again in cycle.
> >> > >
> >> > > I have used Vmware Vsphere 5.1 SDK for building CS.
> >> > >
> >> > > The error logs give this error:
> >> > >
> >> > > 2014-09-16 16:11:01,619 WARN  [c.c.h.v.r.VmwareResource]
> >> > > (DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd:
> >> > > StartCommand) StartCommand failed due to Exception:
> >> > > java.lang.NullPointerException
> >> > > Message: null
> >> > >
> 

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

I'm not getting far enough along in the process to repro (or not) the
problem.

I do have a /mnt/sec folder (and I even made it 777).

Any thoughts on this?

WARN  [c.c.s.r.VmwareStorageProcessor] (DirectAgent-46:ctx-fdd23ec9
192.168.129.71, job-95/job-123, cmd: CopyCommand) Exception: tar
--no-same-owner -xf /mnt/sec/template/tmpl/1/8//routing-8.ova
java.io.IOException: Cannot run program "tar" (in directory
"/mnt/sec/template/tmpl/1/8"): error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041)
at com.cloud.utils.script.Script.execute(Script.java:195)
at com.cloud.utils.script.Script.execute(Script.java:163)
at com.cloud.storage.res

On Wed, Sep 17, 2014 at 2:53 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> You're right, Marcus. Now that I think about it, asserts are ignored by
> default.
>
> On Wed, Sep 17, 2014 at 1:59 PM, Marcus  wrote:
>
>> Aren't asserts ignored by default? I think we had an issue with asserts in
>> the past, and I believe at the time the default config had asserts
>> disabled.
>>
>>
>> On Wed, Sep 17, 2014 at 1:35 PM, Ritu Sabharwal 
>> wrote:
>>
>> > Hi Mike,
>> >
>> > I updated the master just now and tried the setup. I see the same error
>> on
>> > same line number.
>> >
>> > Thanks & Regards,
>> > Ritu S.
>> >
>> > -Original Message-
>> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> > Sent: Tuesday, September 16, 2014 8:32 PM
>> > To: dev@cloudstack.apache.org
>> > Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
>> > Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs
>> > with Vmware setup with CS server
>> >
>> > Can you tell us what commit SHA you are running under?
>> >
>> > I just updated master and line 2094 in VmwareResource is the following:
>> >
>> > String[] diskChain = diskInfo.getDiskChain();
>> >
>> > The only candidate for a NullPointerException there is diskInfo;
>> however,
>> > the previous line would have caught this as it looks like this:
>> >
>> > assert (diskInfo != null);
>> >
>> > That being the case, I'm curious what commit SHA you saw this on?
>> >
>> > Thanks!
>> >
>> > On Tue, Sep 16, 2014 at 5:22 PM, Ritu Sabharwal 
>> > wrote:
>> >
>> > > Hi Sateesh, Koushik,
>> > >
>> > > I am setting up Vmware Cluster with CS (master) and seeing errors.
>> > > ilya was helping me for this setup and figured out this error.
>> > >
>> > > The System VMs(Secondary Stogare VM and Console Proxy VM) are not
>> > > coming up properly. The system vms are reconfiguring and destroying
>> > > again and again in cycle.
>> > >
>> > > I have used Vmware Vsphere 5.1 SDK for building CS.
>> > >
>> > > The error logs give this error:
>> > >
>> > > 2014-09-16 16:11:01,619 WARN  [c.c.h.v.r.VmwareResource]
>> > > (DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd:
>> > > StartCommand) StartCommand failed due to Exception:
>> > > java.lang.NullPointerException
>> > > Message: null
>> > >
>> > > java.lang.NullPointerException
>> > > at
>> > >
>> >
>> com.cloud.hypervisor.vmware.resource.VmwareResource.postDiskConfigBeforeStart(VmwareResource.java:2094)
>> > > at
>> > >
>> >
>> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:1685)
>> > > at
>> > >
>> >
>> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:448)
>> > > at
>> > >
>> >
>> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:294)
>> > > at
>> > >
>> >
>> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
>> > > at
>> > >
>> >
>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
>> > > at
>> > >
>> >
>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
>> > > at
>> > >
>> >
>> org.apac

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

The instructions to seed secondary storage for VMware look like this:

/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt \
-m /mnt/secondary \
-u 
http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
\
-h vmware \
-s  \
-F

For -m, I have /export/secondary (not /mnt/secondary). I assume that's
correct because that is, in fact, where my secondary storage system
template is located for XenServer and that seems to work just fine.


On Thu, Sep 18, 2014 at 3:20 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> I'm not getting far enough along in the process to repro (or not) the
> problem.
>
> I do have a /mnt/sec folder (and I even made it 777).
>
> Any thoughts on this?
>
> WARN  [c.c.s.r.VmwareStorageProcessor] (DirectAgent-46:ctx-fdd23ec9
> 192.168.129.71, job-95/job-123, cmd: CopyCommand) Exception: tar
> --no-same-owner -xf /mnt/sec/template/tmpl/1/8//routing-8.ova
> java.io.IOException: Cannot run program "tar" (in directory
> "/mnt/sec/template/tmpl/1/8"): error=2, No such file or directory
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041)
> at com.cloud.utils.script.Script.execute(Script.java:195)
> at com.cloud.utils.script.Script.execute(Script.java:163)
> at com.cloud.storage.res
>
> On Wed, Sep 17, 2014 at 2:53 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> You're right, Marcus. Now that I think about it, asserts are ignored by
>> default.
>>
>> On Wed, Sep 17, 2014 at 1:59 PM, Marcus  wrote:
>>
>>> Aren't asserts ignored by default? I think we had an issue with asserts
>>> in
>>> the past, and I believe at the time the default config had asserts
>>> disabled.
>>>
>>>
>>> On Wed, Sep 17, 2014 at 1:35 PM, Ritu Sabharwal 
>>> wrote:
>>>
>>> > Hi Mike,
>>> >
>>> > I updated the master just now and tried the setup. I see the same
>>> error on
>>> > same line number.
>>> >
>>> > Thanks & Regards,
>>> > Ritu S.
>>> >
>>> > -Original Message-
>>> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>>> > Sent: Tuesday, September 16, 2014 8:32 PM
>>> > To: dev@cloudstack.apache.org
>>> > Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
>>> > Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs
>>> > with Vmware setup with CS server
>>> >
>>> > Can you tell us what commit SHA you are running under?
>>> >
>>> > I just updated master and line 2094 in VmwareResource is the following:
>>> >
>>> > String[] diskChain = diskInfo.getDiskChain();
>>> >
>>> > The only candidate for a NullPointerException there is diskInfo;
>>> however,
>>> > the previous line would have caught this as it looks like this:
>>> >
>>> > assert (diskInfo != null);
>>> >
>>> > That being the case, I'm curious what commit SHA you saw this on?
>>> >
>>> > Thanks!
>>> >
>>> > On Tue, Sep 16, 2014 at 5:22 PM, Ritu Sabharwal 
>>> > wrote:
>>> >
>>> > > Hi Sateesh, Koushik,
>>> > >
>>> > > I am setting up Vmware Cluster with CS (master) and seeing errors.
>>> > > ilya was helping me for this setup and figured out this error.
>>> > >
>>> > > The System VMs(Secondary Stogare VM and Console Proxy VM) are not
>>> > > coming up properly. The system vms are reconfiguring and destroying
>>> > > again and again in cycle.
>>> > >
>>> > > I have used Vmware Vsphere 5.1 SDK for building CS.
>>> > >
>>> > > The error logs give this error:
>>> > >
>>> > > 2014-09-16 16:11:01,619 WARN  [c.c.h.v.r.VmwareResource]
>>> > > (DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd:
>>> > > StartCommand) StartCommand failed due to Exception:
>>> > > java.lang.NullPointerException
>>> > > Message: null
>>> > >
>>> > > java.lang.NullPointerException
>>> > > at
>>> > >
>>> >
>>> com.cloud.hypervisor.vmware.resource.VmwareResource.postDiskConfigBeforeStart(VmwareResource.java:2094)
>>> > > at
>>> > >
>>> >
>>> com.clou

RE: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Ritu Sabharwal]

I have an external NFS server and it is mounted to /mnt/secondary on my CS 
server so seeding command I used is:

/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt  
-m /mnt/secondary  -u 
http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
-h vmware -F

I guess, if the secondary storage is local, then /export/secondary should be 
fine.

Regards,
Ritu S.
-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] 
Sent: Thursday, September 18, 2014 2:34 PM
To: dev@cloudstack.apache.org
Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with 
Vmware setup with CS server

The instructions to seed secondary storage for VMware look like this:

/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt 
\ -m /mnt/secondary \ -u 
http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
\
-h vmware \
-s  \ -F

For -m, I have /export/secondary (not /mnt/secondary). I assume that's correct 
because that is, in fact, where my secondary storage system template is located 
for XenServer and that seems to work just fine.


On Thu, Sep 18, 2014 at 3:20 PM, Mike Tutkowski < mike.tutkow...@solidfire.com> 
wrote:

> I'm not getting far enough along in the process to repro (or not) the 
> problem.
>
> I do have a /mnt/sec folder (and I even made it 777).
>
> Any thoughts on this?
>
> WARN  [c.c.s.r.VmwareStorageProcessor] (DirectAgent-46:ctx-fdd23ec9 
> 192.168.129.71, job-95/job-123, cmd: CopyCommand) Exception: tar 
> --no-same-owner -xf /mnt/sec/template/tmpl/1/8//routing-8.ova
> java.io.IOException: Cannot run program "tar" (in directory
> "/mnt/sec/template/tmpl/1/8"): error=2, No such file or directory
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041)
> at com.cloud.utils.script.Script.execute(Script.java:195)
> at com.cloud.utils.script.Script.execute(Script.java:163)
> at com.cloud.storage.res
>
> On Wed, Sep 17, 2014 at 2:53 PM, Mike Tutkowski < 
> mike.tutkow...@solidfire.com> wrote:
>
>> You're right, Marcus. Now that I think about it, asserts are ignored 
>> by default.
>>
>> On Wed, Sep 17, 2014 at 1:59 PM, Marcus  wrote:
>>
>>> Aren't asserts ignored by default? I think we had an issue with 
>>> asserts in the past, and I believe at the time the default config 
>>> had asserts disabled.
>>>
>>>
>>> On Wed, Sep 17, 2014 at 1:35 PM, Ritu Sabharwal 
>>> 
>>> wrote:
>>>
>>> > Hi Mike,
>>> >
>>> > I updated the master just now and tried the setup. I see the same
>>> error on
>>> > same line number.
>>> >
>>> > Thanks & Regards,
>>> > Ritu S.
>>> >
>>> > -Original Message-
>>> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>>> > Sent: Tuesday, September 16, 2014 8:32 PM
>>> > To: dev@cloudstack.apache.org
>>> > Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
>>> > Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up 
>>> > System VMs with Vmware setup with CS server
>>> >
>>> > Can you tell us what commit SHA you are running under?
>>> >
>>> > I just updated master and line 2094 in VmwareResource is the following:
>>> >
>>> > String[] diskChain = diskInfo.getDiskChain();
>>> >
>>> > The only candidate for a NullPointerException there is diskInfo;
>>> however,
>>> > the previous line would have caught this as it looks like this:
>>> >
>>> > assert (diskInfo != null);
>>> >
>>> > That being the case, I'm curious what commit SHA you saw this on?
>>> >
>>> > Thanks!
>>> >
>>> > On Tue, Sep 16, 2014 at 5:22 PM, Ritu Sabharwal 
>>> > 
>>> > wrote:
>>> >
>>> > > Hi Sateesh, Koushik,
>>> > >
>>> > > I am setting up Vmware Cluster with CS (master) and seeing errors.
>>> > > ilya was helping me for this setup and figured out this error.
>>> > >
>>> > > The System VMs(Secondary Stogare VM and Console Proxy VM) are 
>>> > > not coming up properly. The system vms are reconfiguring and 
>>> > > destroying again and again in cycle.
>>> > >
>>> > > I have used Vmware Vsphere 5.1 SDK for building CS.
>>> > >
>>> > >

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

Yeah, I've been through the instructions a couple times and don't see
anything that indicates why it's having trouble with /mnt/sec (it says
/mnt/sec instead of /mnt/secondary in the log messages).

On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal 
wrote:

> I have an external NFS server and it is mounted to /mnt/secondary on my CS
> server so seeding command I used is:
>
> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
> -m /mnt/secondary  -u
> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
> -h vmware -F
>
> I guess, if the secondary storage is local, then /export/secondary should
> be fine.
>
> Regards,
> Ritu S.
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Thursday, September 18, 2014 2:34 PM
> To: dev@cloudstack.apache.org
> Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs
> with Vmware setup with CS server
>
> The instructions to seed secondary storage for VMware look like this:
>
> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
> \ -m /mnt/secondary \ -u
> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
> \
> -h vmware \
> -s  \ -F
>
> For -m, I have /export/secondary (not /mnt/secondary). I assume that's
> correct because that is, in fact, where my secondary storage system
> template is located for XenServer and that seems to work just fine.
>
>
> On Thu, Sep 18, 2014 at 3:20 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
> > I'm not getting far enough along in the process to repro (or not) the
> > problem.
> >
> > I do have a /mnt/sec folder (and I even made it 777).
> >
> > Any thoughts on this?
> >
> > WARN  [c.c.s.r.VmwareStorageProcessor] (DirectAgent-46:ctx-fdd23ec9
> > 192.168.129.71, job-95/job-123, cmd: CopyCommand) Exception: tar
> > --no-same-owner -xf /mnt/sec/template/tmpl/1/8//routing-8.ova
> > java.io.IOException: Cannot run program "tar" (in directory
> > "/mnt/sec/template/tmpl/1/8"): error=2, No such file or directory
> > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041)
> > at com.cloud.utils.script.Script.execute(Script.java:195)
> > at com.cloud.utils.script.Script.execute(Script.java:163)
> > at com.cloud.storage.res
> >
> > On Wed, Sep 17, 2014 at 2:53 PM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com> wrote:
> >
> >> You're right, Marcus. Now that I think about it, asserts are ignored
> >> by default.
> >>
> >> On Wed, Sep 17, 2014 at 1:59 PM, Marcus  wrote:
> >>
> >>> Aren't asserts ignored by default? I think we had an issue with
> >>> asserts in the past, and I believe at the time the default config
> >>> had asserts disabled.
> >>>
> >>>
> >>> On Wed, Sep 17, 2014 at 1:35 PM, Ritu Sabharwal
> >>> 
> >>> wrote:
> >>>
> >>> > Hi Mike,
> >>> >
> >>> > I updated the master just now and tried the setup. I see the same
> >>> error on
> >>> > same line number.
> >>> >
> >>> > Thanks & Regards,
> >>> > Ritu S.
> >>> >
> >>> > -Original Message-
> >>> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> >>> > Sent: Tuesday, September 16, 2014 8:32 PM
> >>> > To: dev@cloudstack.apache.org
> >>> > Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
> >>> > Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up
> >>> > System VMs with Vmware setup with CS server
> >>> >
> >>> > Can you tell us what commit SHA you are running under?
> >>> >
> >>> > I just updated master and line 2094 in VmwareResource is the
> following:
> >>> >
> >>> > String[] diskChain = diskInfo.getDiskChain();
> >>> >
> >>> > The only candidate for a NullPointerException there is diskInfo;
> >>> however,
> >>> > the previous line would have caught this as it looks like this:
> >>> >
> >>> > assert (diskInfo != null);
> >>> >
> >>> > That being the case, I'm curious what commit SHA you saw this on?
> >>> >
> >>> > Thanks!
> >>> 

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

The instructions even say the following:

If your secondary storage mount point is not named /mnt/secondary,
substitute your own mount point name.

On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Yeah, I've been through the instructions a couple times and don't see
> anything that indicates why it's having trouble with /mnt/sec (it says
> /mnt/sec instead of /mnt/secondary in the log messages).
>
> On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal 
> wrote:
>
>> I have an external NFS server and it is mounted to /mnt/secondary on my
>> CS server so seeding command I used is:
>>
>> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>> -m /mnt/secondary  -u
>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
>> -h vmware -F
>>
>> I guess, if the secondary storage is local, then /export/secondary should
>> be fine.
>>
>> Regards,
>> Ritu S.
>> -Original Message-
>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> Sent: Thursday, September 18, 2014 2:34 PM
>> To: dev@cloudstack.apache.org
>> Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
>> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs
>> with Vmware setup with CS server
>>
>> The instructions to seed secondary storage for VMware look like this:
>>
>> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>> \ -m /mnt/secondary \ -u
>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
>> \
>> -h vmware \
>> -s  \ -F
>>
>> For -m, I have /export/secondary (not /mnt/secondary). I assume that's
>> correct because that is, in fact, where my secondary storage system
>> template is located for XenServer and that seems to work just fine.
>>
>>
>> On Thu, Sep 18, 2014 at 3:20 PM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>> > I'm not getting far enough along in the process to repro (or not) the
>> > problem.
>> >
>> > I do have a /mnt/sec folder (and I even made it 777).
>> >
>> > Any thoughts on this?
>> >
>> > WARN  [c.c.s.r.VmwareStorageProcessor] (DirectAgent-46:ctx-fdd23ec9
>> > 192.168.129.71, job-95/job-123, cmd: CopyCommand) Exception: tar
>> > --no-same-owner -xf /mnt/sec/template/tmpl/1/8//routing-8.ova
>> > java.io.IOException: Cannot run program "tar" (in directory
>> > "/mnt/sec/template/tmpl/1/8"): error=2, No such file or directory
>> > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041)
>> > at com.cloud.utils.script.Script.execute(Script.java:195)
>> > at com.cloud.utils.script.Script.execute(Script.java:163)
>> > at com.cloud.storage.res
>> >
>> > On Wed, Sep 17, 2014 at 2:53 PM, Mike Tutkowski <
>> > mike.tutkow...@solidfire.com> wrote:
>> >
>> >> You're right, Marcus. Now that I think about it, asserts are ignored
>> >> by default.
>> >>
>> >> On Wed, Sep 17, 2014 at 1:59 PM, Marcus  wrote:
>> >>
>> >>> Aren't asserts ignored by default? I think we had an issue with
>> >>> asserts in the past, and I believe at the time the default config
>> >>> had asserts disabled.
>> >>>
>> >>>
>> >>> On Wed, Sep 17, 2014 at 1:35 PM, Ritu Sabharwal
>> >>> 
>> >>> wrote:
>> >>>
>> >>> > Hi Mike,
>> >>> >
>> >>> > I updated the master just now and tried the setup. I see the same
>> >>> error on
>> >>> > same line number.
>> >>> >
>> >>> > Thanks & Regards,
>> >>> > Ritu S.
>> >>> >
>> >>> > -Original Message-
>> >>> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> >>> > Sent: Tuesday, September 16, 2014 8:32 PM
>> >>> > To: dev@cloudstack.apache.org
>> >>> > Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
>> >>> > Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up
>> >>> > System VMs with Vmware setup with CS server
>> >>> >
>> >>> > Can you tell us what commit SHA you are running under?
>> >>> >
>> >>> > I just update

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

I think I found the magic. :)

sudo mount -t nfs 192.168.129.46:/export/secondary /mnt/sec

If I mount /export/secondary to /mnt/sec (I did it in a bit of a roundabout
way here), then the management server is happy.

I think this is only VMware "thing" for the management server.

Does anyone know if we document this?

Thanks!

On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> The instructions even say the following:
>
> If your secondary storage mount point is not named /mnt/secondary,
> substitute your own mount point name.
>
> On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> Yeah, I've been through the instructions a couple times and don't see
>> anything that indicates why it's having trouble with /mnt/sec (it says
>> /mnt/sec instead of /mnt/secondary in the log messages).
>>
>> On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal 
>> wrote:
>>
>>> I have an external NFS server and it is mounted to /mnt/secondary on my
>>> CS server so seeding command I used is:
>>>
>>> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>>> -m /mnt/secondary  -u
>>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
>>> -h vmware -F
>>>
>>> I guess, if the secondary storage is local, then /export/secondary
>>> should be fine.
>>>
>>> Regards,
>>> Ritu S.
>>> -Original Message-
>>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>>> Sent: Thursday, September 18, 2014 2:34 PM
>>> To: dev@cloudstack.apache.org
>>> Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
>>> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs
>>> with Vmware setup with CS server
>>>
>>> The instructions to seed secondary storage for VMware look like this:
>>>
>>> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>>> \ -m /mnt/secondary \ -u
>>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
>>> \
>>> -h vmware \
>>> -s  \ -F
>>>
>>> For -m, I have /export/secondary (not /mnt/secondary). I assume that's
>>> correct because that is, in fact, where my secondary storage system
>>> template is located for XenServer and that seems to work just fine.
>>>
>>>
>>> On Thu, Sep 18, 2014 at 3:20 PM, Mike Tutkowski <
>>> mike.tutkow...@solidfire.com> wrote:
>>>
>>> > I'm not getting far enough along in the process to repro (or not) the
>>> > problem.
>>> >
>>> > I do have a /mnt/sec folder (and I even made it 777).
>>> >
>>> > Any thoughts on this?
>>> >
>>> > WARN  [c.c.s.r.VmwareStorageProcessor] (DirectAgent-46:ctx-fdd23ec9
>>> > 192.168.129.71, job-95/job-123, cmd: CopyCommand) Exception: tar
>>> > --no-same-owner -xf /mnt/sec/template/tmpl/1/8//routing-8.ova
>>> > java.io.IOException: Cannot run program "tar" (in directory
>>> > "/mnt/sec/template/tmpl/1/8"): error=2, No such file or directory
>>> > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041)
>>> > at com.cloud.utils.script.Script.execute(Script.java:195)
>>> > at com.cloud.utils.script.Script.execute(Script.java:163)
>>> > at com.cloud.storage.res
>>> >
>>> > On Wed, Sep 17, 2014 at 2:53 PM, Mike Tutkowski <
>>> > mike.tutkow...@solidfire.com> wrote:
>>> >
>>> >> You're right, Marcus. Now that I think about it, asserts are ignored
>>> >> by default.
>>> >>
>>> >> On Wed, Sep 17, 2014 at 1:59 PM, Marcus  wrote:
>>> >>
>>> >>> Aren't asserts ignored by default? I think we had an issue with
>>> >>> asserts in the past, and I believe at the time the default config
>>> >>> had asserts disabled.
>>> >>>
>>> >>>
>>> >>> On Wed, Sep 17, 2014 at 1:35 PM, Ritu Sabharwal
>>> >>> 
>>> >>> wrote:
>>> >>>
>>> >>> > Hi Mike,
>>> >>> >
>>> >>> > I updated the master just now and tried the setup. I see the same
>>> >>> error on
>>> >>> > same line number.
>>> >>> >

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

Just a little update on this:

The problem doesn't seem to have anything to do with "managed" storage code
that was introduced back in March.

The dsName is derived from the UUID of the datastore. This leads to a null
being returned from diskInfoBuilder.getDiskInfoByBackingFileBaseName, which
subsequently leads to a null being returned from this method (and a
NullPointerException being thrown).

I plan to take a look at the history of this file in gitk.

private VirtualMachineDiskInfo
getMatchingExistingDisk(VirtualMachineDiskInfoBuilder diskInfoBuilder,
DiskTO vol) {

if (diskInfoBuilder != null) {

VolumeObjectTO volume = (VolumeObjectTO)vol.getData();

String dsName = volume.getDataStore().getUuid().replace("-", ""
);


Map details = vol.getDetails();

boolean isManaged = details != null &&
Boolean.parseBoolean(details.get(DiskTO.MANAGED));


VirtualMachineDiskInfo diskInfo =


diskInfoBuilder.getDiskInfoByBackingFileBaseName(isManaged ? new
DatastoreFile(volume.getPath()).getFileBaseName() : volume.getPath(),
dsName);

On Thu, Sep 18, 2014 at 4:34 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> I think I found the magic. :)
>
> sudo mount -t nfs 192.168.129.46:/export/secondary /mnt/sec
>
> If I mount /export/secondary to /mnt/sec (I did it in a bit of a
> roundabout way here), then the management server is happy.
>
> I think this is only VMware "thing" for the management server.
>
> Does anyone know if we document this?
>
> Thanks!
>
> On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> The instructions even say the following:
>>
>> If your secondary storage mount point is not named /mnt/secondary,
>> substitute your own mount point name.
>>
>> On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>>> Yeah, I've been through the instructions a couple times and don't see
>>> anything that indicates why it's having trouble with /mnt/sec (it says
>>> /mnt/sec instead of /mnt/secondary in the log messages).
>>>
>>> On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal 
>>> wrote:
>>>
>>>> I have an external NFS server and it is mounted to /mnt/secondary on my
>>>> CS server so seeding command I used is:
>>>>
>>>> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>>>> -m /mnt/secondary  -u
>>>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
>>>> -h vmware -F
>>>>
>>>> I guess, if the secondary storage is local, then /export/secondary
>>>> should be fine.
>>>>
>>>> Regards,
>>>> Ritu S.
>>>> -Original Message-
>>>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>>>> Sent: Thursday, September 18, 2014 2:34 PM
>>>> To: dev@cloudstack.apache.org
>>>> Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
>>>> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs
>>>> with Vmware setup with CS server
>>>>
>>>> The instructions to seed secondary storage for VMware look like this:
>>>>
>>>> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>>>> \ -m /mnt/secondary \ -u
>>>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
>>>> \
>>>> -h vmware \
>>>> -s  \ -F
>>>>
>>>> For -m, I have /export/secondary (not /mnt/secondary). I assume that's
>>>> correct because that is, in fact, where my secondary storage system
>>>> template is located for XenServer and that seems to work just fine.
>>>>
>>>>
>>>> On Thu, Sep 18, 2014 at 3:20 PM, Mike Tutkowski <
>>>> mike.tutkow...@solidfire.com> wrote:
>>>>
>>>> > I'm not getting far enough along in the process to repro (or not) the
>>>> > problem.
>>>> >
>>>> > I do have a /mnt/sec folder (and I even made it 777).
>>>> >
>>>> > Any thoughts on this?
>>>> >
>>>> > WARN  [c.c.s.r.VmwareStorageProcessor] (DirectAgent-46:ctx-fdd23ec9
>>>> > 192.168.129.71, job-95/job-123, cmd: CopyCommand) Exception: tar
>>>> > --no-same-owner -xf /mnt/sec/template/tmpl/1/8//routing-8.ova
>>>> > java.io.IOE

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

Little clarification on this:

"The dsName is derived from the UUID of the datastore."

I mean that the dsName is derived from the UUID primary storage in the DB.

On Thu, Sep 18, 2014 at 5:12 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Just a little update on this:
>
> The problem doesn't seem to have anything to do with "managed" storage
> code that was introduced back in March.
>
> The dsName is derived from the UUID of the datastore. This leads to a null
> being returned from diskInfoBuilder.getDiskInfoByBackingFileBaseName, which
> subsequently leads to a null being returned from this method (and a
> NullPointerException being thrown).
>
> I plan to take a look at the history of this file in gitk.
>
> private VirtualMachineDiskInfo
> getMatchingExistingDisk(VirtualMachineDiskInfoBuilder diskInfoBuilder,
> DiskTO vol) {
>
> if (diskInfoBuilder != null) {
>
> VolumeObjectTO volume = (VolumeObjectTO)vol.getData();
>
> String dsName = volume.getDataStore().getUuid().replace("-",
> "");
>
>
> Map details = vol.getDetails();
>
> boolean isManaged = details != null &&
> Boolean.parseBoolean(details.get(DiskTO.MANAGED));
>
>
> VirtualMachineDiskInfo diskInfo =
>
>
> diskInfoBuilder.getDiskInfoByBackingFileBaseName(isManaged ? new
> DatastoreFile(volume.getPath()).getFileBaseName() : volume.getPath(),
> dsName);
>
> On Thu, Sep 18, 2014 at 4:34 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> I think I found the magic. :)
>>
>> sudo mount -t nfs 192.168.129.46:/export/secondary /mnt/sec
>>
>> If I mount /export/secondary to /mnt/sec (I did it in a bit of a
>> roundabout way here), then the management server is happy.
>>
>> I think this is only VMware "thing" for the management server.
>>
>> Does anyone know if we document this?
>>
>> Thanks!
>>
>> On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>>> The instructions even say the following:
>>>
>>> If your secondary storage mount point is not named /mnt/secondary,
>>> substitute your own mount point name.
>>>
>>> On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski <
>>> mike.tutkow...@solidfire.com> wrote:
>>>
>>>> Yeah, I've been through the instructions a couple times and don't see
>>>> anything that indicates why it's having trouble with /mnt/sec (it says
>>>> /mnt/sec instead of /mnt/secondary in the log messages).
>>>>
>>>> On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal 
>>>> wrote:
>>>>
>>>>> I have an external NFS server and it is mounted to /mnt/secondary on
>>>>> my CS server so seeding command I used is:
>>>>>
>>>>> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>>>>> -m /mnt/secondary  -u
>>>>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
>>>>> -h vmware -F
>>>>>
>>>>> I guess, if the secondary storage is local, then /export/secondary
>>>>> should be fine.
>>>>>
>>>>> Regards,
>>>>> Ritu S.
>>>>> -Original Message-
>>>>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>>>>> Sent: Thursday, September 18, 2014 2:34 PM
>>>>> To: dev@cloudstack.apache.org
>>>>> Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
>>>>> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System
>>>>> VMs with Vmware setup with CS server
>>>>>
>>>>> The instructions to seed secondary storage for VMware look like this:
>>>>>
>>>>> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>>>>> \ -m /mnt/secondary \ -u
>>>>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
>>>>> \
>>>>> -h vmware \
>>>>> -s  \ -F
>>>>>
>>>>> For -m, I have /export/secondary (not /mnt/secondary). I assume that's
>>>>> correct because that is, in fact, where my secondary storage system
>>>>> template is located for XenServer and that seems to work just fine.
>>>>>
>>>>>
>>>>> On Thu, Se

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

I agree with Ilya. This commit seems to be a likely candidate for this
issue:

8bb4022f3729154f85036c4a7f55e2de783e4909

In this commit dsName is added and assigned to the UUID of the applicable
primary storage (minus any hyphens in the UUID).

I don't think this will match the name of a datastore in this case.

On Tue, Sep 16, 2014 at 6:32 PM, ilya musayev 
wrote:

> ++ Likitha Shetty
>
> Ritu,
>
> Please confirm that you've are running latest/synced master branch?
>
> I've noticed a commit by Likitha that may be relevant:
>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=
> 8bb4022f3729154f85036c4a7f55e2de783e4909
>
> Regards
> ilya
>
> On 9/16/14, 4:22 PM, Ritu Sabharwal wrote:
>
>>
>> Hi Sateesh, Koushik,
>>
>> I am setting up Vmware Cluster with CS (master) and seeing errors. ilya
>> was helping me for this setup and figured out this error.
>>
>> The System VMs(Secondary Stogare VM and Console Proxy VM) are not coming
>> up properly. The system vms are reconfiguring and destroying again and
>> again in cycle.
>>
>> I have used Vmware Vsphere 5.1 SDK for building CS.
>>
>> The error logs give this error:
>>
>> 2014-09-16 16:11:01,619 WARN  [c.c.h.v.r.VmwareResource]
>> (DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd: StartCommand)
>> StartCommand failed due to Exception: java.lang.NullPointerException
>>
>> Message: null
>>
>> java.lang.NullPointerException
>>
>> at com.cloud.hypervisor.vmware.resource.VmwareResource.
>> postDiskConfigBeforeStart(VmwareResource.java:2094)
>>
>> at com.cloud.hypervisor.vmware.resource.VmwareResource.
>> execute(VmwareResource.java:1685)
>>
>> at com.cloud.hypervisor.vmware.resource.VmwareResource.
>> executeRequest(VmwareResource.java:448)
>>
>> at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(
>> DirectAgentAttache.java:294)
>>
>> at org.apache.cloudstack.managed.context.
>> ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
>>
>> at org.apache.cloudstack.managed.context.impl.
>> DefaultManagedContext$1.call(DefaultManagedContext.java:56)
>>
>> at org.apache.cloudstack.managed.context.impl.
>> DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
>>
>> at org.apache.cloudstack.managed.context.impl.
>> DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
>>
>> at org.apache.cloudstack.managed.context.
>> ManagedContextRunnable.run(ManagedContextRunnable.java:46)
>>
>> at java.util.concurrent.Executors$RunnableAdapter.
>> call(Executors.java:471)
>>
>> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>>
>> at java.util.concurrent.ScheduledThreadPoolExecutor$
>> ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
>>
>> at java.util.concurrent.ScheduledThreadPoolExecutor$
>> ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>>
>> 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:744)
>>
>> Please help to resolve this issue.
>>
>> Thanks & Regards,
>>
>> Ritu S.
>>
>>
>


-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
*™*

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

If I revert 8bb4022f3729154f85036c4a7f55e2de783e4909, it seems to go back
to working.

I think the problem is the code should use this method to get the datastore
object and then ask the datastore object for its name:

HypervisorHostHelper.findDatastoreWithBackwardsCompatibility

On Thu, Sep 18, 2014 at 5:36 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> I agree with Ilya. This commit seems to be a likely candidate for this
> issue:
>
> 8bb4022f3729154f85036c4a7f55e2de783e4909
>
> In this commit dsName is added and assigned to the UUID of the applicable
> primary storage (minus any hyphens in the UUID).
>
> I don't think this will match the name of a datastore in this case.
>
> On Tue, Sep 16, 2014 at 6:32 PM, ilya musayev 
> wrote:
>
>> ++ Likitha Shetty
>>
>> Ritu,
>>
>> Please confirm that you've are running latest/synced master branch?
>>
>> I've noticed a commit by Likitha that may be relevant:
>>
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=
>> 8bb4022f3729154f85036c4a7f55e2de783e4909
>>
>> Regards
>> ilya
>>
>> On 9/16/14, 4:22 PM, Ritu Sabharwal wrote:
>>
>>>
>>> Hi Sateesh, Koushik,
>>>
>>> I am setting up Vmware Cluster with CS (master) and seeing errors. ilya
>>> was helping me for this setup and figured out this error.
>>>
>>> The System VMs(Secondary Stogare VM and Console Proxy VM) are not coming
>>> up properly. The system vms are reconfiguring and destroying again and
>>> again in cycle.
>>>
>>> I have used Vmware Vsphere 5.1 SDK for building CS.
>>>
>>> The error logs give this error:
>>>
>>> 2014-09-16 16:11:01,619 WARN  [c.c.h.v.r.VmwareResource]
>>> (DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd: StartCommand)
>>> StartCommand failed due to Exception: java.lang.NullPointerException
>>>
>>> Message: null
>>>
>>> java.lang.NullPointerException
>>>
>>> at com.cloud.hypervisor.vmware.resource.VmwareResource.
>>> postDiskConfigBeforeStart(VmwareResource.java:2094)
>>>
>>> at com.cloud.hypervisor.vmware.resource.VmwareResource.
>>> execute(VmwareResource.java:1685)
>>>
>>> at com.cloud.hypervisor.vmware.resource.VmwareResource.
>>> executeRequest(VmwareResource.java:448)
>>>
>>> at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(
>>> DirectAgentAttache.java:294)
>>>
>>> at org.apache.cloudstack.managed.context.
>>> ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
>>>
>>> at org.apache.cloudstack.managed.context.impl.
>>> DefaultManagedContext$1.call(DefaultManagedContext.java:56)
>>>
>>> at org.apache.cloudstack.managed.context.impl.
>>> DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
>>>
>>> at org.apache.cloudstack.managed.context.impl.
>>> DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
>>>
>>> at org.apache.cloudstack.managed.context.
>>> ManagedContextRunnable.run(ManagedContextRunnable.java:46)
>>>
>>> at java.util.concurrent.Executors$RunnableAdapter.
>>> call(Executors.java:471)
>>>
>>> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>>>
>>> at java.util.concurrent.ScheduledThreadPoolExecutor$
>>> ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
>>>
>>> at java.util.concurrent.ScheduledThreadPoolExecutor$
>>> ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>>>
>>> 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:744)
>>>
>>> Please help to resolve this issue.
>>>
>>> Thanks & Regards,
>>>
>>> Ritu S.
>>>
>>>
>>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> *™*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
*™*

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

Just destroyed and re-created my env from scratch without
8bb4022f3729154f85036c4a7f55e2de783e4909 and it works fine.

I think I know what the author was intending with the code that is causing
the problem, so I'll go ahead and put in what I think is a fix, re-create
my env, and see if it works.

On Thu, Sep 18, 2014 at 6:26 PM, ilya musayev 
wrote:

>  Thank you Mike, please keep us posted.
>
> Regards
> ilya
>
> On 9/18/14, 4:14 PM, Mike Tutkowski wrote:
>
> Little clarification on this:
>
>  "The dsName is derived from the UUID of the datastore."
>
>  I mean that the dsName is derived from the UUID primary storage in the
> DB.
>
> On Thu, Sep 18, 2014 at 5:12 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> Just a little update on this:
>>
>>  The problem doesn't seem to have anything to do with "managed" storage
>> code that was introduced back in March.
>>
>>  The dsName is derived from the UUID of the datastore. This leads to a
>> null being returned from diskInfoBuilder.getDiskInfoByBackingFileBaseName,
>> which subsequently leads to a null being returned from this method (and a
>> NullPointerException being thrown).
>>
>>  I plan to take a look at the history of this file in gitk.
>>
>> private VirtualMachineDiskInfo
>> getMatchingExistingDisk(VirtualMachineDiskInfoBuilder diskInfoBuilder,
>> DiskTO vol) {
>>
>> if (diskInfoBuilder != null) {
>>
>> VolumeObjectTO volume = (VolumeObjectTO)vol.getData();
>>
>> String dsName = volume.getDataStore().getUuid().replace("-",
>> "");
>>
>>
>>  Map details = vol.getDetails();
>>
>> boolean isManaged = details != null &&
>> Boolean.parseBoolean(details.get(DiskTO.MANAGED));
>>
>>
>>  VirtualMachineDiskInfo diskInfo =
>>
>>
>> diskInfoBuilder.getDiskInfoByBackingFileBaseName(isManaged ? new
>> DatastoreFile(volume.getPath()).getFileBaseName() : volume.getPath(),
>> dsName);
>>
>> On Thu, Sep 18, 2014 at 4:34 PM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>>> I think I found the magic. :)
>>>
>>> sudo mount -t nfs 192.168.129.46:/export/secondary /mnt/sec
>>>
>>> If I mount /export/secondary to /mnt/sec (I did it in a bit of a
>>> roundabout way here), then the management server is happy.
>>>
>>> I think this is only VMware "thing" for the management server.
>>>
>>> Does anyone know if we document this?
>>>
>>> Thanks!
>>>
>>> On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski <
>>> mike.tutkow...@solidfire.com> wrote:
>>>
>>>> The instructions even say the following:
>>>>
>>>>  If your secondary storage mount point is not named /mnt/secondary,
>>>> substitute your own mount point name.
>>>>
>>>> On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski <
>>>> mike.tutkow...@solidfire.com> wrote:
>>>>
>>>>> Yeah, I've been through the instructions a couple times and don't see
>>>>> anything that indicates why it's having trouble with /mnt/sec (it says
>>>>> /mnt/sec instead of /mnt/secondary in the log messages).
>>>>>
>>>>> On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal 
>>>>> wrote:
>>>>>
>>>>>> I have an external NFS server and it is mounted to /mnt/secondary on
>>>>>> my CS server so seeding command I used is:
>>>>>>
>>>>>> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>>>>>> -m /mnt/secondary  -u
>>>>>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
>>>>>> -h vmware -F
>>>>>>
>>>>>> I guess, if the secondary storage is local, then /export/secondary
>>>>>> should be fine.
>>>>>>
>>>>>> Regards,
>>>>>> Ritu S.
>>>>>> -Original Message-
>>>>>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>>>>>>  Sent: Thursday, September 18, 2014 2:34 PM
>>>>>> To: dev@cloudstack.apache.org
>>>>>> Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
>>>>>> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up Syst

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[ilya musayev]

Thank you Mike, please keep us posted.

Regards
ilya
On 9/18/14, 4:14 PM, Mike Tutkowski wrote:

Little clarification on this:

"The dsName is derived from the UUID of the datastore."

I mean that the dsName is derived from the UUID primary storage in the DB.

On Thu, Sep 18, 2014 at 5:12 PM, Mike Tutkowski 
mailto:mike.tutkow...@solidfire.com>> 
wrote:


Just a little update on this:

The problem doesn't seem to have anything to do with "managed"
storage code that was introduced back in March.

The dsName is derived from the UUID of the datastore. This leads
to a null being returned from
diskInfoBuilder.getDiskInfoByBackingFileBaseName, which
subsequently leads to a null being returned from this method (and
a NullPointerException being thrown).

I plan to take a look at the history of this file in gitk.

private VirtualMachineDiskInfo
getMatchingExistingDisk(VirtualMachineDiskInfoBuilder
diskInfoBuilder, DiskTO vol) {

if (diskInfoBuilder != null) {

VolumeObjectTO volume = (VolumeObjectTO)vol.getData();

String dsName =
volume.getDataStore().getUuid().replace("-", "");


Map details = vol.getDetails();

boolean isManaged = details != null &&
Boolean.parseBoolean(details.get(DiskTO.MANAGED));


VirtualMachineDiskInfo diskInfo =

diskInfoBuilder.getDiskInfoByBackingFileBaseName(isManaged ? new
DatastoreFile(volume.getPath()).getFileBaseName() :
volume.getPath(), dsName);


On Thu, Sep 18, 2014 at 4:34 PM, Mike Tutkowski
mailto:mike.tutkow...@solidfire.com>> wrote:

I think I found the magic. :)

sudo mount -t nfs 192.168.129.46:/export/secondary /mnt/sec

If I mount /export/secondary to /mnt/sec (I did it in a bit of
a roundabout way here), then the management server is happy.

I think this is only VMware "thing" for the management server.

Does anyone know if we document this?

Thanks!


On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski
mailto:mike.tutkow...@solidfire.com>> wrote:

The instructions even say the following:

If your secondary storage mount point is not named
/mnt/secondary, substitute your own mount point name.

On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski
mailto:mike.tutkow...@solidfire.com>> wrote:

Yeah, I've been through the instructions a couple
times and don't see anything that indicates why it's
having trouble with /mnt/sec (it says /mnt/sec instead
of /mnt/secondary in the log messages).

On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal
mailto:rsabh...@brocade.com>>
wrote:

I have an external NFS server and it is mounted to
/mnt/secondary on my CS server so seeding command
I used is:


/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
-m /mnt/secondary -u

http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
-h vmware -F

I guess, if the secondary storage is local, then
/export/secondary should be fine.

Regards,
Ritu S.
-Original Message-
From: Mike Tutkowski
[mailto:mike.tutkow...@solidfire.com
<mailto:mike.tutkow...@solidfire.com>]
Sent: Thursday, September 18, 2014 2:34 PM
To: dev@cloudstack.apache.org
<mailto:dev@cloudstack.apache.org>
    Cc: ilya musayev; Koushik Das; Sateesh
Chodapuneedi; Adip Shetty
            Subject: Re: [VMWARE SETUP ERROR] Error seeing in
brining up System VMs with Vmware setup with CS server

The instructions to seed secondary storage for
VMware look like this:


/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
\ -m /mnt/secondary \ -u

http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
\
-h vmware \
-s  \ -F

For -m, I have /export/secondary (not
/mnt/secondary). I assume that's correct because
that is, in fact, where my secondary storage
system template is located for XenServer and that
seems to work just fine.


On Thu, Sep 1

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

OK, I checked in a fix for this:

https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;h=18e5aa116e99906f24a292bf7546809e05c72ec2;hp=7537c33bcdda65672fdd8f81509e6885aa536932

I did notice that both before and after my fix that the virtual router is
NOT coming up.

The system VM being cloned and the starting of the VM looks fine. It gets
to the command prompt and then a little while later is shut down and
restarted. I get an error in the GUI indicating that my VM deployment
failed.

I don't personally know a whole lot about how the virtual router code
works, so we should pass that on to an appropriate developer.

On Thu, Sep 18, 2014 at 6:35 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Just destroyed and re-created my env from scratch without
> 8bb4022f3729154f85036c4a7f55e2de783e4909 and it works fine.
>
> I think I know what the author was intending with the code that is causing
> the problem, so I'll go ahead and put in what I think is a fix, re-create
> my env, and see if it works.
>
> On Thu, Sep 18, 2014 at 6:26 PM, ilya musayev 
> wrote:
>
>>  Thank you Mike, please keep us posted.
>>
>> Regards
>> ilya
>>
>> On 9/18/14, 4:14 PM, Mike Tutkowski wrote:
>>
>> Little clarification on this:
>>
>>  "The dsName is derived from the UUID of the datastore."
>>
>>  I mean that the dsName is derived from the UUID primary storage in the
>> DB.
>>
>> On Thu, Sep 18, 2014 at 5:12 PM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>>> Just a little update on this:
>>>
>>>  The problem doesn't seem to have anything to do with "managed" storage
>>> code that was introduced back in March.
>>>
>>>  The dsName is derived from the UUID of the datastore. This leads to a
>>> null being returned from diskInfoBuilder.getDiskInfoByBackingFileBaseName,
>>> which subsequently leads to a null being returned from this method (and a
>>> NullPointerException being thrown).
>>>
>>>  I plan to take a look at the history of this file in gitk.
>>>
>>> private VirtualMachineDiskInfo
>>> getMatchingExistingDisk(VirtualMachineDiskInfoBuilder diskInfoBuilder,
>>> DiskTO vol) {
>>>
>>> if (diskInfoBuilder != null) {
>>>
>>> VolumeObjectTO volume = (VolumeObjectTO)vol.getData();
>>>
>>> String dsName = volume.getDataStore().getUuid().replace("-",
>>> "");
>>>
>>>
>>>  Map details = vol.getDetails();
>>>
>>> boolean isManaged = details != null &&
>>> Boolean.parseBoolean(details.get(DiskTO.MANAGED));
>>>
>>>
>>>  VirtualMachineDiskInfo diskInfo =
>>>
>>>
>>> diskInfoBuilder.getDiskInfoByBackingFileBaseName(isManaged ? new
>>> DatastoreFile(volume.getPath()).getFileBaseName() : volume.getPath(),
>>> dsName);
>>>
>>> On Thu, Sep 18, 2014 at 4:34 PM, Mike Tutkowski <
>>> mike.tutkow...@solidfire.com> wrote:
>>>
>>>> I think I found the magic. :)
>>>>
>>>> sudo mount -t nfs 192.168.129.46:/export/secondary /mnt/sec
>>>>
>>>> If I mount /export/secondary to /mnt/sec (I did it in a bit of a
>>>> roundabout way here), then the management server is happy.
>>>>
>>>> I think this is only VMware "thing" for the management server.
>>>>
>>>> Does anyone know if we document this?
>>>>
>>>> Thanks!
>>>>
>>>> On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski <
>>>> mike.tutkow...@solidfire.com> wrote:
>>>>
>>>>> The instructions even say the following:
>>>>>
>>>>>  If your secondary storage mount point is not named /mnt/secondary,
>>>>> substitute your own mount point name.
>>>>>
>>>>> On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski <
>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>
>>>>>> Yeah, I've been through the instructions a couple times and don't see
>>>>>> anything that indicates why it's having trouble with /mnt/sec (it says
>>>>>> /mnt/sec instead of /mnt/secondary in the log messages).
>>>>>>
>>>>>> On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal >>>>> > wrote:
>>>>>>
>>>>>>>

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

point name.
>>>>>>
>>>>>> On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski <
>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>
>>>>>>> Yeah, I've been through the instructions a couple times and don't
>>>>>>> see anything that indicates why it's having trouble with /mnt/sec (it 
>>>>>>> says
>>>>>>> /mnt/sec instead of /mnt/secondary in the log messages).
>>>>>>>
>>>>>>> On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal <
>>>>>>> rsabh...@brocade.com> wrote:
>>>>>>>
>>>>>>>> I have an external NFS server and it is mounted to /mnt/secondary
>>>>>>>> on my CS server so seeding command I used is:
>>>>>>>>
>>>>>>>> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>>>>>>>> -m /mnt/secondary  -u
>>>>>>>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
>>>>>>>> -h vmware -F
>>>>>>>>
>>>>>>>> I guess, if the secondary storage is local, then /export/secondary
>>>>>>>> should be fine.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Ritu S.
>>>>>>>> -Original Message-
>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>>>>>>>>  Sent: Thursday, September 18, 2014 2:34 PM
>>>>>>>> To: dev@cloudstack.apache.org
>>>>>>>> Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
>>>>>>>> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System
>>>>>>>> VMs with Vmware setup with CS server
>>>>>>>>
>>>>>>>> The instructions to seed secondary storage for VMware look like
>>>>>>>> this:
>>>>>>>>
>>>>>>>> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>>>>>>>> \ -m /mnt/secondary \ -u
>>>>>>>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
>>>>>>>> \
>>>>>>>> -h vmware \
>>>>>>>> -s  \ -F
>>>>>>>>
>>>>>>>> For -m, I have /export/secondary (not /mnt/secondary). I assume
>>>>>>>> that's correct because that is, in fact, where my secondary storage 
>>>>>>>> system
>>>>>>>> template is located for XenServer and that seems to work just fine.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Sep 18, 2014 at 3:20 PM, Mike Tutkowski <
>>>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>>>
>>>>>>>> > I'm not getting far enough along in the process to repro (or not)
>>>>>>>> the
>>>>>>>> > problem.
>>>>>>>> >
>>>>>>>> > I do have a /mnt/sec folder (and I even made it 777).
>>>>>>>> >
>>>>>>>> > Any thoughts on this?
>>>>>>>> >
>>>>>>>> > WARN  [c.c.s.r.VmwareStorageProcessor]
>>>>>>>> (DirectAgent-46:ctx-fdd23ec9
>>>>>>>> > 192.168.129.71, job-95/job-123, cmd: CopyCommand) Exception: tar
>>>>>>>> > --no-same-owner -xf /mnt/sec/template/tmpl/1/8//routing-8.ova
>>>>>>>> > java.io.IOException: Cannot run program "tar" (in directory
>>>>>>>> > "/mnt/sec/template/tmpl/1/8"): error=2, No such file or directory
>>>>>>>> > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041)
>>>>>>>> > at com.cloud.utils.script.Script.execute(Script.java:195)
>>>>>>>> > at com.cloud.utils.script.Script.execute(Script.java:163)
>>>>>>>> > at com.cloud.storage.res
>>>>>>>> >
>>>>>>>> > On Wed, Sep 17, 2014 at 2:53 PM, Mike Tutkowski <
>>>>>>>> > mike.tutkow...@solidfire.com> wrote:
>>>>>>>>

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

 /export/secondary to /mnt/sec (I did it in a bit of a
>>>>>> roundabout way here), then the management server is happy.
>>>>>>
>>>>>> I think this is only VMware "thing" for the management server.
>>>>>>
>>>>>> Does anyone know if we document this?
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski <
>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>
>>>>>>> The instructions even say the following:
>>>>>>>
>>>>>>>  If your secondary storage mount point is not named /mnt/secondary,
>>>>>>> substitute your own mount point name.
>>>>>>>
>>>>>>> On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski <
>>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>>
>>>>>>>> Yeah, I've been through the instructions a couple times and don't
>>>>>>>> see anything that indicates why it's having trouble with /mnt/sec (it 
>>>>>>>> says
>>>>>>>> /mnt/sec instead of /mnt/secondary in the log messages).
>>>>>>>>
>>>>>>>> On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal <
>>>>>>>> rsabh...@brocade.com> wrote:
>>>>>>>>
>>>>>>>>> I have an external NFS server and it is mounted to /mnt/secondary
>>>>>>>>> on my CS server so seeding command I used is:
>>>>>>>>>
>>>>>>>>> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>>>>>>>>> -m /mnt/secondary  -u
>>>>>>>>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
>>>>>>>>> -h vmware -F
>>>>>>>>>
>>>>>>>>> I guess, if the secondary storage is local, then /export/secondary
>>>>>>>>> should be fine.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Ritu S.
>>>>>>>>> -Original Message-
>>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>>>>>>>>>  Sent: Thursday, September 18, 2014 2:34 PM
>>>>>>>>> To: dev@cloudstack.apache.org
>>>>>>>>> Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
>>>>>>>>> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up
>>>>>>>>> System VMs with Vmware setup with CS server
>>>>>>>>>
>>>>>>>>> The instructions to seed secondary storage for VMware look like
>>>>>>>>> this:
>>>>>>>>>
>>>>>>>>> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>>>>>>>>> \ -m /mnt/secondary \ -u
>>>>>>>>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
>>>>>>>>> \
>>>>>>>>> -h vmware \
>>>>>>>>> -s  \ -F
>>>>>>>>>
>>>>>>>>> For -m, I have /export/secondary (not /mnt/secondary). I assume
>>>>>>>>> that's correct because that is, in fact, where my secondary storage 
>>>>>>>>> system
>>>>>>>>> template is located for XenServer and that seems to work just fine.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, Sep 18, 2014 at 3:20 PM, Mike Tutkowski <
>>>>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>>>>
>>>>>>>>> > I'm not getting far enough along in the process to repro (or
>>>>>>>>> not) the
>>>>>>>>> > problem.
>>>>>>>>> >
>>>>>>>>> > I do have a /mnt/sec folder (and I even made it 777).
>>>>>>>>> >
>>>>>>>>> > Any thoughts on this?
>>>>>>>>> >
>>>>>>>>> > WARN  [c.c.s.r.VmwareStorageProce

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

ails != null &&
>>>>>> Boolean.parseBoolean(details.get(DiskTO.MANAGED));
>>>>>>
>>>>>>
>>>>>>  VirtualMachineDiskInfo diskInfo =
>>>>>>
>>>>>>
>>>>>> diskInfoBuilder.getDiskInfoByBackingFileBaseName(isManaged ? new
>>>>>> DatastoreFile(volume.getPath()).getFileBaseName() : volume.getPath(),
>>>>>> dsName);
>>>>>>
>>>>>> On Thu, Sep 18, 2014 at 4:34 PM, Mike Tutkowski <
>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>
>>>>>>> I think I found the magic. :)
>>>>>>>
>>>>>>> sudo mount -t nfs 192.168.129.46:/export/secondary /mnt/sec
>>>>>>>
>>>>>>> If I mount /export/secondary to /mnt/sec (I did it in a bit of a
>>>>>>> roundabout way here), then the management server is happy.
>>>>>>>
>>>>>>> I think this is only VMware "thing" for the management server.
>>>>>>>
>>>>>>> Does anyone know if we document this?
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski <
>>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>>
>>>>>>>> The instructions even say the following:
>>>>>>>>
>>>>>>>>  If your secondary storage mount point is not named
>>>>>>>> /mnt/secondary, substitute your own mount point name.
>>>>>>>>
>>>>>>>> On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski <
>>>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>>>
>>>>>>>>> Yeah, I've been through the instructions a couple times and don't
>>>>>>>>> see anything that indicates why it's having trouble with /mnt/sec (it 
>>>>>>>>> says
>>>>>>>>> /mnt/sec instead of /mnt/secondary in the log messages).
>>>>>>>>>
>>>>>>>>> On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal <
>>>>>>>>> rsabh...@brocade.com> wrote:
>>>>>>>>>
>>>>>>>>>> I have an external NFS server and it is mounted to /mnt/secondary
>>>>>>>>>> on my CS server so seeding command I used is:
>>>>>>>>>>
>>>>>>>>>> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>>>>>>>>>> -m /mnt/secondary  -u
>>>>>>>>>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
>>>>>>>>>> -h vmware -F
>>>>>>>>>>
>>>>>>>>>> I guess, if the secondary storage is local, then
>>>>>>>>>> /export/secondary should be fine.
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Ritu S.
>>>>>>>>>> -Original Message-
>>>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>>>>>>>>>>  Sent: Thursday, September 18, 2014 2:34 PM
>>>>>>>>>> To: dev@cloudstack.apache.org
>>>>>>>>>> Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
>>>>>>>>>> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up
>>>>>>>>>> System VMs with Vmware setup with CS server
>>>>>>>>>>
>>>>>>>>>> The instructions to seed secondary storage for VMware look like
>>>>>>>>>> this:
>>>>>>>>>>
>>>>>>>>>> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>>>>>>>>>> \ -m /mnt/secondary \ -u
>>>>>>>>>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
>>>>>>>>>> \
>>>>>>>>>> -h vmware \
>>>>>>>>>> -s  \ -F
>>>>>>>>>>
>>>>>>>>>> For -m, I have 

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Erik Weber]

gt;>>> I think this is only VMware "thing" for the management server.
> >>>>>
> >>>>> Does anyone know if we document this?
> >>>>>
> >>>>> Thanks!
> >>>>>
> >>>>> On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski <
> >>>>> mike.tutkow...@solidfire.com> wrote:
> >>>>>
> >>>>>> The instructions even say the following:
> >>>>>>
> >>>>>>  If your secondary storage mount point is not named /mnt/secondary,
> >>>>>> substitute your own mount point name.
> >>>>>>
> >>>>>> On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski <
> >>>>>> mike.tutkow...@solidfire.com> wrote:
> >>>>>>
> >>>>>>> Yeah, I've been through the instructions a couple times and don't
> >>>>>>> see anything that indicates why it's having trouble with /mnt/sec
> (it says
> >>>>>>> /mnt/sec instead of /mnt/secondary in the log messages).
> >>>>>>>
> >>>>>>> On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal <
> >>>>>>> rsabh...@brocade.com> wrote:
> >>>>>>>
> >>>>>>>> I have an external NFS server and it is mounted to /mnt/secondary
> >>>>>>>> on my CS server so seeding command I used is:
> >>>>>>>>
> >>>>>>>>
> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
> >>>>>>>> -m /mnt/secondary  -u
> >>>>>>>>
> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
> >>>>>>>> -h vmware -F
> >>>>>>>>
> >>>>>>>> I guess, if the secondary storage is local, then /export/secondary
> >>>>>>>> should be fine.
> >>>>>>>>
> >>>>>>>> Regards,
> >>>>>>>> Ritu S.
> >>>>>>>> -Original Message-
> >>>>>>>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> >>>>>>>>  Sent: Thursday, September 18, 2014 2:34 PM
> >>>>>>>> To: dev@cloudstack.apache.org
> >>>>>>>> Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
> >>>>>>>> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up
> System
> >>>>>>>> VMs with Vmware setup with CS server
> >>>>>>>>
> >>>>>>>> The instructions to seed secondary storage for VMware look like
> >>>>>>>> this:
> >>>>>>>>
> >>>>>>>>
> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
> >>>>>>>> \ -m /mnt/secondary \ -u
> >>>>>>>>
> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
> >>>>>>>> \
> >>>>>>>> -h vmware \
> >>>>>>>> -s  \ -F
> >>>>>>>>
> >>>>>>>> For -m, I have /export/secondary (not /mnt/secondary). I assume
> >>>>>>>> that's correct because that is, in fact, where my secondary
> storage system
> >>>>>>>> template is located for XenServer and that seems to work just
> fine.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Thu, Sep 18, 2014 at 3:20 PM, Mike Tutkowski <
> >>>>>>>> mike.tutkow...@solidfire.com> wrote:
> >>>>>>>>
> >>>>>>>> > I'm not getting far enough along in the process to repro (or
> not)
> >>>>>>>> the
> >>>>>>>> > problem.
> >>>>>>>> >
> >>>>>>>> > I do have a /mnt/sec folder (and I even made it 777).
> >>>>>>>> >
> >>>>>>>> > Any thoughts on this?
> >>>>>>>> >
> >>>>>>>> > WARN  [c.c.s.r.VmwareStorageProcessor]
> >>>>>>>> (DirectAgent-46:ctx-fdd23ec9
> >>>>>>>> > 192.168.129.71

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

? new
> > >>>> DatastoreFile(volume.getPath()).getFileBaseName() :
> volume.getPath(),
> > >>>> dsName);
> > >>>>
> > >>>> On Thu, Sep 18, 2014 at 4:34 PM, Mike Tutkowski <
> > >>>> mike.tutkow...@solidfire.com> wrote:
> > >>>>
> > >>>>> I think I found the magic. :)
> > >>>>>
> > >>>>> sudo mount -t nfs 192.168.129.46:/export/secondary /mnt/sec
> > >>>>>
> > >>>>> If I mount /export/secondary to /mnt/sec (I did it in a bit of a
> > >>>>> roundabout way here), then the management server is happy.
> > >>>>>
> > >>>>> I think this is only VMware "thing" for the management server.
> > >>>>>
> > >>>>> Does anyone know if we document this?
> > >>>>>
> > >>>>> Thanks!
> > >>>>>
> > >>>>> On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski <
> > >>>>> mike.tutkow...@solidfire.com> wrote:
> > >>>>>
> > >>>>>> The instructions even say the following:
> > >>>>>>
> > >>>>>>  If your secondary storage mount point is not named
> /mnt/secondary,
> > >>>>>> substitute your own mount point name.
> > >>>>>>
> > >>>>>> On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski <
> > >>>>>> mike.tutkow...@solidfire.com> wrote:
> > >>>>>>
> > >>>>>>> Yeah, I've been through the instructions a couple times and don't
> > >>>>>>> see anything that indicates why it's having trouble with /mnt/sec
> > (it says
> > >>>>>>> /mnt/sec instead of /mnt/secondary in the log messages).
> > >>>>>>>
> > >>>>>>> On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal <
> > >>>>>>> rsabh...@brocade.com> wrote:
> > >>>>>>>
> > >>>>>>>> I have an external NFS server and it is mounted to
> /mnt/secondary
> > >>>>>>>> on my CS server so seeding command I used is:
> > >>>>>>>>
> > >>>>>>>>
> >
> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
> > >>>>>>>> -m /mnt/secondary  -u
> > >>>>>>>>
> >
> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
> > >>>>>>>> -h vmware -F
> > >>>>>>>>
> > >>>>>>>> I guess, if the secondary storage is local, then
> /export/secondary
> > >>>>>>>> should be fine.
> > >>>>>>>>
> > >>>>>>>> Regards,
> > >>>>>>>> Ritu S.
> > >>>>>>>> -Original Message-
> > >>>>>>>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > >>>>>>>>  Sent: Thursday, September 18, 2014 2:34 PM
> > >>>>>>>> To: dev@cloudstack.apache.org
> > >>>>>>>> Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
> > >>>>>>>> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up
> > System
> > >>>>>>>> VMs with Vmware setup with CS server
> > >>>>>>>>
> > >>>>>>>> The instructions to seed secondary storage for VMware look like
> > >>>>>>>> this:
> > >>>>>>>>
> > >>>>>>>>
> >
> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
> > >>>>>>>> \ -m /mnt/secondary \ -u
> > >>>>>>>>
> >
> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
> > >>>>>>>> \
> > >>>>>>>> -h vmware \
> > >>>>>>>> -s  \ -F
> > >>>>>>>>
> > >>>>>>>> For -m, I have /export/secondary (not /mnt/secondary). I assume
> > >>>>>>>> that's correct because that is, in fact, wher

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Amogh Vasekar]

tTO)vol.getData();
>> > >>>>
>> > >>>> String dsName =
>> > volume.getDataStore().getUuid().replace("-",
>> > >>>> "");
>> > >>>>
>> > >>>>
>> > >>>>  Map details = vol.getDetails();
>> > >>>>
>> > >>>> boolean isManaged = details != null &&
>> > >>>> Boolean.parseBoolean(details.get(DiskTO.MANAGED));
>> > >>>>
>> > >>>>
>> > >>>>  VirtualMachineDiskInfo diskInfo =
>> > >>>>
>> > >>>>
>> > >>>> diskInfoBuilder.getDiskInfoByBackingFileBaseName(isManaged ? new
>> > >>>> DatastoreFile(volume.getPath()).getFileBaseName() :
>> volume.getPath(),
>> > >>>> dsName);
>> > >>>>
>> > >>>> On Thu, Sep 18, 2014 at 4:34 PM, Mike Tutkowski <
>> > >>>> mike.tutkow...@solidfire.com> wrote:
>> > >>>>
>> > >>>>> I think I found the magic. :)
>> > >>>>>
>> > >>>>> sudo mount -t nfs 192.168.129.46:/export/secondary /mnt/sec
>> > >>>>>
>> > >>>>> If I mount /export/secondary to /mnt/sec (I did it in a bit of a
>> > >>>>> roundabout way here), then the management server is happy.
>> > >>>>>
>> > >>>>> I think this is only VMware "thing" for the management server.
>> > >>>>>
>> > >>>>> Does anyone know if we document this?
>> > >>>>>
>> > >>>>> Thanks!
>> > >>>>>
>> > >>>>> On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski <
>> > >>>>> mike.tutkow...@solidfire.com> wrote:
>> > >>>>>
>> > >>>>>> The instructions even say the following:
>> > >>>>>>
>> > >>>>>>  If your secondary storage mount point is not named
>> /mnt/secondary,
>> > >>>>>> substitute your own mount point name.
>> > >>>>>>
>> > >>>>>> On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski <
>> > >>>>>> mike.tutkow...@solidfire.com> wrote:
>> > >>>>>>
>> > >>>>>>> Yeah, I've been through the instructions a couple times and
>>don't
>> > >>>>>>> see anything that indicates why it's having trouble with
>>/mnt/sec
>> > (it says
>> > >>>>>>> /mnt/sec instead of /mnt/secondary in the log messages).
>> > >>>>>>>
>> > >>>>>>> On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal <
>> > >>>>>>> rsabh...@brocade.com> wrote:
>> > >>>>>>>
>> > >>>>>>>> I have an external NFS server and it is mounted to
>> /mnt/secondary
>> > >>>>>>>> on my CS server so seeding command I used is:
>> > >>>>>>>>
>> > >>>>>>>>
>> >
>> 
>>/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-
>>tmplt
>> > >>>>>>>> -m /mnt/secondary  -u
>> > >>>>>>>>
>> >
>> 
>>http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmwa
>>re.ova
>> > >>>>>>>> -h vmware -F
>> > >>>>>>>>
>> > >>>>>>>> I guess, if the secondary storage is local, then
>> /export/secondary
>> > >>>>>>>> should be fine.
>> > >>>>>>>>
>> > >>>>>>>> Regards,
>> > >>>>>>>> Ritu S.
>> > >>>>>>>> -Original Message-
>> > >>>>>>>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> > >>>>>>>>  Sent: Thursday, September 18, 2014 2:34 PM
>> > >>>>>>>> To: dev@cloudstack.apache.org
>> > >>>>>>>> Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip
>>Shetty
>> > 

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

ll being returned from this
> >>method
> >> > (and a
> >> > >>>> NullPointerException being thrown).
> >> > >>>>
> >> > >>>>  I plan to take a look at the history of this file in gitk.
> >> > >>>>
> >> > >>>> private VirtualMachineDiskInfo
> >> > >>>> getMatchingExistingDisk(VirtualMachineDiskInfoBuilder
> >> diskInfoBuilder,
> >> > >>>> DiskTO vol) {
> >> > >>>>
> >> > >>>> if (diskInfoBuilder != null) {
> >> > >>>>
> >> > >>>> VolumeObjectTO volume =
> >>(VolumeObjectTO)vol.getData();
> >> > >>>>
> >> > >>>> String dsName =
> >> > volume.getDataStore().getUuid().replace("-",
> >> > >>>> "");
> >> > >>>>
> >> > >>>>
> >> > >>>>  Map details = vol.getDetails();
> >> > >>>>
> >> > >>>> boolean isManaged = details != null &&
> >> > >>>> Boolean.parseBoolean(details.get(DiskTO.MANAGED));
> >> > >>>>
> >> > >>>>
> >> > >>>>  VirtualMachineDiskInfo diskInfo =
> >> > >>>>
> >> > >>>>
> >> > >>>> diskInfoBuilder.getDiskInfoByBackingFileBaseName(isManaged ? new
> >> > >>>> DatastoreFile(volume.getPath()).getFileBaseName() :
> >> volume.getPath(),
> >> > >>>> dsName);
> >> > >>>>
> >> > >>>> On Thu, Sep 18, 2014 at 4:34 PM, Mike Tutkowski <
> >> > >>>> mike.tutkow...@solidfire.com> wrote:
> >> > >>>>
> >> > >>>>> I think I found the magic. :)
> >> > >>>>>
> >> > >>>>> sudo mount -t nfs 192.168.129.46:/export/secondary /mnt/sec
> >> > >>>>>
> >> > >>>>> If I mount /export/secondary to /mnt/sec (I did it in a bit of a
> >> > >>>>> roundabout way here), then the management server is happy.
> >> > >>>>>
> >> > >>>>> I think this is only VMware "thing" for the management server.
> >> > >>>>>
> >> > >>>>> Does anyone know if we document this?
> >> > >>>>>
> >> > >>>>> Thanks!
> >> > >>>>>
> >> > >>>>> On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski <
> >> > >>>>> mike.tutkow...@solidfire.com> wrote:
> >> > >>>>>
> >> > >>>>>> The instructions even say the following:
> >> > >>>>>>
> >> > >>>>>>  If your secondary storage mount point is not named
> >> /mnt/secondary,
> >> > >>>>>> substitute your own mount point name.
> >> > >>>>>>
> >> > >>>>>> On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski <
> >> > >>>>>> mike.tutkow...@solidfire.com> wrote:
> >> > >>>>>>
> >> > >>>>>>> Yeah, I've been through the instructions a couple times and
> >>don't
> >> > >>>>>>> see anything that indicates why it's having trouble with
> >>/mnt/sec
> >> > (it says
> >> > >>>>>>> /mnt/sec instead of /mnt/secondary in the log messages).
> >> > >>>>>>>
> >> > >>>>>>> On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal <
> >> > >>>>>>> rsabh...@brocade.com> wrote:
> >> > >>>>>>>
> >> > >>>>>>>> I have an external NFS server and it is mounted to
> >> /mnt/secondary
> >> > >>>>>>>> on my CS server so seeding command I used is:
> >> > >>>>>>>>
> >> > >>>>>>>>
> >> >
> >>
> >>/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-
> >>tmplt
> >> 

RE: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Ritu Sabharwal]

Hi Mike,

Thanks for trying out this and the investigation.

I hope the developer for system vm would pick up this issue and help to resolve.

Thanks & Regards,
Ritu S.

-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Friday, September 19, 2014 9:01 AM
To: dev@cloudstack.apache.org
Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with 
Vmware setup with CS server

http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-vmware.ova

On Fri, Sep 19, 2014 at 9:58 AM, Erik Weber  wrote:

> Which systemvm template are you using?
>
> Erik
> 19. sep. 2014 03:47 skrev "Mike Tutkowski"
> 
> følgende:
>
> > Actually, the virtual router says it requires an upgrade.
> >
> > I think I can just turn that check off and re-run my create-VM test.
> >
> > On Thu, Sep 18, 2014 at 7:43 PM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com> wrote:
> >
> > > OK, I checked in a fix for this:
> > >
> > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;
> h=18e5aa116e99906f24a292bf7546809e05c72ec2;hp=7537c33bcdda65672fdd8f81
> 509e6885aa536932
> > >
> > > I did notice that both before and after my fix that the virtual
> > > router
> is
> > > NOT coming up.
> > >
> > > The system VM being cloned and the starting of the VM looks fine.
> > > It
> gets
> > > to the command prompt and then a little while later is shut down
> > > and restarted. I get an error in the GUI indicating that my VM
> > > deployment failed.
> > >
> > > I don't personally know a whole lot about how the virtual router
> > > code works, so we should pass that on to an appropriate developer.
> > >
> > > On Thu, Sep 18, 2014 at 6:35 PM, Mike Tutkowski <
> > > mike.tutkow...@solidfire.com> wrote:
> > >
> > >> Just destroyed and re-created my env from scratch without
> > >> 8bb4022f3729154f85036c4a7f55e2de783e4909 and it works fine.
> > >>
> > >> I think I know what the author was intending with the code that
> > >> is causing the problem, so I'll go ahead and put in what I think
> > >> is a
> fix,
> > >> re-create my env, and see if it works.
> > >>
> > >> On Thu, Sep 18, 2014 at 6:26 PM, ilya musayev
> > >>  >
> > >> wrote:
> > >>
> > >>>  Thank you Mike, please keep us posted.
> > >>>
> > >>> Regards
> > >>> ilya
> > >>>
> > >>> On 9/18/14, 4:14 PM, Mike Tutkowski wrote:
> > >>>
> > >>> Little clarification on this:
> > >>>
> > >>>  "The dsName is derived from the UUID of the datastore."
> > >>>
> > >>>  I mean that the dsName is derived from the UUID primary storage
> > >>> in
> the
> > >>> DB.
> > >>>
> > >>> On Thu, Sep 18, 2014 at 5:12 PM, Mike Tutkowski <
> > >>> mike.tutkow...@solidfire.com> wrote:
> > >>>
> > >>>> Just a little update on this:
> > >>>>
> > >>>>  The problem doesn't seem to have anything to do with "managed"
> > >>>> storage code that was introduced back in March.
> > >>>>
> > >>>>  The dsName is derived from the UUID of the datastore. This
> > >>>> leads
> to a
> > >>>> null being returned from
> > diskInfoBuilder.getDiskInfoByBackingFileBaseName,
> > >>>> which subsequently leads to a null being returned from this
> > >>>> method
> > (and a
> > >>>> NullPointerException being thrown).
> > >>>>
> > >>>>  I plan to take a look at the history of this file in gitk.
> > >>>>
> > >>>> private VirtualMachineDiskInfo
> > >>>> getMatchingExistingDisk(VirtualMachineDiskInfoBuilder
> diskInfoBuilder,
> > >>>> DiskTO vol) {
> > >>>>
> > >>>> if (diskInfoBuilder != null) {
> > >>>>
> > >>>> VolumeObjectTO volume =
> > >>>> (VolumeObjectTO)vol.getData();
> > >>>>
> > >>>> String dsName =
> > volume.getDataStore().getUuid().replace("-&

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

No problem :)

The one issue is fixed now. We just need to have someone check out what's
going on with the virtual router.

On Fri, Sep 19, 2014 at 5:21 PM, Ritu Sabharwal 
wrote:

> Hi Mike,
>
> Thanks for trying out this and the investigation.
>
> I hope the developer for system vm would pick up this issue and help to
> resolve.
>
> Thanks & Regards,
> Ritu S.
>
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Friday, September 19, 2014 9:01 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs
> with Vmware setup with CS server
>
>
> http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-vmware.ova
>
> On Fri, Sep 19, 2014 at 9:58 AM, Erik Weber  wrote:
>
> > Which systemvm template are you using?
> >
> > Erik
> > 19. sep. 2014 03:47 skrev "Mike Tutkowski"
> > 
> > følgende:
> >
> > > Actually, the virtual router says it requires an upgrade.
> > >
> > > I think I can just turn that check off and re-run my create-VM test.
> > >
> > > On Thu, Sep 18, 2014 at 7:43 PM, Mike Tutkowski <
> > > mike.tutkow...@solidfire.com> wrote:
> > >
> > > > OK, I checked in a fix for this:
> > > >
> > > >
> > > >
> > >
> > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;
> > h=18e5aa116e99906f24a292bf7546809e05c72ec2;hp=7537c33bcdda65672fdd8f81
> > 509e6885aa536932
> > > >
> > > > I did notice that both before and after my fix that the virtual
> > > > router
> > is
> > > > NOT coming up.
> > > >
> > > > The system VM being cloned and the starting of the VM looks fine.
> > > > It
> > gets
> > > > to the command prompt and then a little while later is shut down
> > > > and restarted. I get an error in the GUI indicating that my VM
> > > > deployment failed.
> > > >
> > > > I don't personally know a whole lot about how the virtual router
> > > > code works, so we should pass that on to an appropriate developer.
> > > >
> > > > On Thu, Sep 18, 2014 at 6:35 PM, Mike Tutkowski <
> > > > mike.tutkow...@solidfire.com> wrote:
> > > >
> > > >> Just destroyed and re-created my env from scratch without
> > > >> 8bb4022f3729154f85036c4a7f55e2de783e4909 and it works fine.
> > > >>
> > > >> I think I know what the author was intending with the code that
> > > >> is causing the problem, so I'll go ahead and put in what I think
> > > >> is a
> > fix,
> > > >> re-create my env, and see if it works.
> > > >>
> > > >> On Thu, Sep 18, 2014 at 6:26 PM, ilya musayev
> > > >>  > >
> > > >> wrote:
> > > >>
> > > >>>  Thank you Mike, please keep us posted.
> > > >>>
> > > >>> Regards
> > > >>> ilya
> > > >>>
> > > >>> On 9/18/14, 4:14 PM, Mike Tutkowski wrote:
> > > >>>
> > > >>> Little clarification on this:
> > > >>>
> > > >>>  "The dsName is derived from the UUID of the datastore."
> > > >>>
> > > >>>  I mean that the dsName is derived from the UUID primary storage
> > > >>> in
> > the
> > > >>> DB.
> > > >>>
> > > >>> On Thu, Sep 18, 2014 at 5:12 PM, Mike Tutkowski <
> > > >>> mike.tutkow...@solidfire.com> wrote:
> > > >>>
> > > >>>> Just a little update on this:
> > > >>>>
> > > >>>>  The problem doesn't seem to have anything to do with "managed"
> > > >>>> storage code that was introduced back in March.
> > > >>>>
> > > >>>>  The dsName is derived from the UUID of the datastore. This
> > > >>>> leads
> > to a
> > > >>>> null being returned from
> > > diskInfoBuilder.getDiskInfoByBackingFileBaseName,
> > > >>>> which subsequently leads to a null being returned from this
> > > >>>> method
> > > (and a
> > > >>>> NullPointerException being thrown).
> &g

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[ilya musayev]

Ritu,

Open a ticket in JIRA as major/blocker for 4.5, so it gets noticed.

You can also try running you code on 4.4 or 4.3.1, but i know it maybe 
too much work to backport.


Mike thank you for spending time trying to figure this out.

Regards
ilya
On 9/19/14, 4:21 PM, Ritu Sabharwal wrote:

Hi Mike,

Thanks for trying out this and the investigation.

I hope the developer for system vm would pick up this issue and help to resolve.

Thanks & Regards,
Ritu S.

-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Friday, September 19, 2014 9:01 AM
To: dev@cloudstack.apache.org
Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with 
Vmware setup with CS server

http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-vmware.ova

On Fri, Sep 19, 2014 at 9:58 AM, Erik Weber  wrote:


Which systemvm template are you using?

Erik
19. sep. 2014 03:47 skrev "Mike Tutkowski"

følgende:


Actually, the virtual router says it requires an upgrade.

I think I can just turn that check off and re-run my create-VM test.

On Thu, Sep 18, 2014 at 7:43 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:


OK, I checked in a fix for this:




https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;
h=18e5aa116e99906f24a292bf7546809e05c72ec2;hp=7537c33bcdda65672fdd8f81
509e6885aa536932

I did notice that both before and after my fix that the virtual
router

is

NOT coming up.

The system VM being cloned and the starting of the VM looks fine.
It

gets

to the command prompt and then a little while later is shut down
and restarted. I get an error in the GUI indicating that my VM
deployment failed.

I don't personally know a whole lot about how the virtual router
code works, so we should pass that on to an appropriate developer.

On Thu, Sep 18, 2014 at 6:35 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:


Just destroyed and re-created my env from scratch without
8bb4022f3729154f85036c4a7f55e2de783e4909 and it works fine.

I think I know what the author was intending with the code that
is causing the problem, so I'll go ahead and put in what I think
is a

fix,

re-create my env, and see if it works.

On Thu, Sep 18, 2014 at 6:26 PM, ilya musayev

  Thank you Mike, please keep us posted.

Regards
ilya

On 9/18/14, 4:14 PM, Mike Tutkowski wrote:

Little clarification on this:

  "The dsName is derived from the UUID of the datastore."

  I mean that the dsName is derived from the UUID primary storage
in

the

DB.

On Thu, Sep 18, 2014 at 5:12 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:


Just a little update on this:

  The problem doesn't seem to have anything to do with "managed"
storage code that was introduced back in March.

  The dsName is derived from the UUID of the datastore. This
leads

to a

null being returned from

diskInfoBuilder.getDiskInfoByBackingFileBaseName,

which subsequently leads to a null being returned from this
method

(and a

NullPointerException being thrown).

  I plan to take a look at the history of this file in gitk.

 private VirtualMachineDiskInfo
getMatchingExistingDisk(VirtualMachineDiskInfoBuilder

diskInfoBuilder,

DiskTO vol) {

 if (diskInfoBuilder != null) {

 VolumeObjectTO volume =
(VolumeObjectTO)vol.getData();

 String dsName =

volume.getDataStore().getUuid().replace("-",

"");


  Map details = vol.getDetails();

 boolean isManaged = details != null &&
Boolean.parseBoolean(details.get(DiskTO.MANAGED));


  VirtualMachineDiskInfo diskInfo =


diskInfoBuilder.getDiskInfoByBackingFileBaseName(isManaged ?
new
DatastoreFile(volume.getPath()).getFileBaseName() :

volume.getPath(),

dsName);

On Thu, Sep 18, 2014 at 4:34 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:


I think I found the magic. :)

sudo mount -t nfs 192.168.129.46:/export/secondary /mnt/sec

If I mount /export/secondary to /mnt/sec (I did it in a bit of
a roundabout way here), then the management server is happy.

I think this is only VMware "thing" for the management server.

Does anyone know if we document this?

Thanks!

On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:


The instructions even say the following:

  If your secondary storage mount point is not named

/mnt/secondary,

substitute your own mount point name.

On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:


Yeah, I've been through the instructions a couple times and
don't see anything that indicates why it's having trouble
with /mnt/sec

(it says

/mnt/sec instead of /mnt/secondary in the log messages).

On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal <
rsabh...@brocade.com> wro

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

Yeah, it's just a coincidence that there were two blocker issues here.

I fixed the one in the compute area, but I don't have much experience with
the virtual router code. It would be more efficient there to find someone
with experience in that area.

On Fri, Sep 19, 2014 at 5:27 PM, ilya musayev 
wrote:

> Ritu,
>
> Open a ticket in JIRA as major/blocker for 4.5, so it gets noticed.
>
> You can also try running you code on 4.4 or 4.3.1, but i know it maybe too
> much work to backport.
>
> Mike thank you for spending time trying to figure this out.
>
> Regards
> ilya
>
> On 9/19/14, 4:21 PM, Ritu Sabharwal wrote:
>
>> Hi Mike,
>>
>> Thanks for trying out this and the investigation.
>>
>> I hope the developer for system vm would pick up this issue and help to
>> resolve.
>>
>> Thanks & Regards,
>> Ritu S.
>>
>> -Original Message-
>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> Sent: Friday, September 19, 2014 9:01 AM
>> To: dev@cloudstack.apache.org
>> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs
>> with Vmware setup with CS server
>>
>> http://jenkins.buildacloud.org/job/build-systemvm64-
>> master/lastSuccessfulBuild/artifact/tools/appliance/dist/
>> systemvm64template-master-vmware.ova
>>
>> On Fri, Sep 19, 2014 at 9:58 AM, Erik Weber  wrote:
>>
>>  Which systemvm template are you using?
>>>
>>> Erik
>>> 19. sep. 2014 03:47 skrev "Mike Tutkowski"
>>> 
>>> følgende:
>>>
>>>  Actually, the virtual router says it requires an upgrade.
>>>>
>>>> I think I can just turn that check off and re-run my create-VM test.
>>>>
>>>> On Thu, Sep 18, 2014 at 7:43 PM, Mike Tutkowski <
>>>> mike.tutkow...@solidfire.com> wrote:
>>>>
>>>>  OK, I checked in a fix for this:
>>>>>
>>>>>
>>>>>
>>>>>  https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff
>>> ;
>>> h=18e5aa116e99906f24a292bf7546809e05c72ec2;hp=7537c33bcdda65672fdd8f81
>>> 509e6885aa536932
>>>
>>>> I did notice that both before and after my fix that the virtual
>>>>> router
>>>>>
>>>> is
>>>
>>>> NOT coming up.
>>>>>
>>>>> The system VM being cloned and the starting of the VM looks fine.
>>>>> It
>>>>>
>>>> gets
>>>
>>>> to the command prompt and then a little while later is shut down
>>>>> and restarted. I get an error in the GUI indicating that my VM
>>>>> deployment failed.
>>>>>
>>>>> I don't personally know a whole lot about how the virtual router
>>>>> code works, so we should pass that on to an appropriate developer.
>>>>>
>>>>> On Thu, Sep 18, 2014 at 6:35 PM, Mike Tutkowski <
>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>
>>>>>  Just destroyed and re-created my env from scratch without
>>>>>> 8bb4022f3729154f85036c4a7f55e2de783e4909 and it works fine.
>>>>>>
>>>>>> I think I know what the author was intending with the code that
>>>>>> is causing the problem, so I'll go ahead and put in what I think
>>>>>> is a
>>>>>>
>>>>> fix,
>>>
>>>> re-create my env, and see if it works.
>>>>>>
>>>>>> On Thu, Sep 18, 2014 at 6:26 PM, ilya musayev
>>>>>> >>>>> wrote:
>>>>>>
>>>>>>Thank you Mike, please keep us posted.
>>>>>>>
>>>>>>> Regards
>>>>>>> ilya
>>>>>>>
>>>>>>> On 9/18/14, 4:14 PM, Mike Tutkowski wrote:
>>>>>>>
>>>>>>> Little clarification on this:
>>>>>>>
>>>>>>>   "The dsName is derived from the UUID of the datastore."
>>>>>>>
>>>>>>>   I mean that the dsName is derived from the UUID primary storage
>>>>>>> in
>>>>>>>
>>>>>> the
>>>
>>>> DB.
>>>>>>>
>>>>>>> On Thu, Sep 18, 2014 at 5:12 PM, Mike Tutkowski <
>>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Abhinandan Prateek]

t;>>>>> 
>>>>>>>boolean isManaged = details != null &&
>>>>>>> Boolean.parseBoolean(details.get(DiskTO.MANAGED));
>>>>>>> 
>>>>>>> 
>>>>>>> VirtualMachineDiskInfo diskInfo =
>>>>>>> 
>>>>>>> 
>>>>>>> diskInfoBuilder.getDiskInfoByBackingFileBaseName(isManaged ? new
>>>>>>> DatastoreFile(volume.getPath()).getFileBaseName() :
>> volume.getPath(),
>>>>>>> dsName);
>>>>>>> 
>>>>>>> On Thu, Sep 18, 2014 at 4:34 PM, Mike Tutkowski <
>>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>> 
>>>>>>>> I think I found the magic. :)
>>>>>>>> 
>>>>>>>> sudo mount -t nfs 192.168.129.46:/export/secondary /mnt/sec
>>>>>>>> 
>>>>>>>> If I mount /export/secondary to /mnt/sec (I did it in a bit of a
>>>>>>>> roundabout way here), then the management server is happy.
>>>>>>>> 
>>>>>>>> I think this is only VMware "thing" for the management server.
>>>>>>>> 
>>>>>>>> Does anyone know if we document this?
>>>>>>>> 
>>>>>>>> Thanks!
>>>>>>>> 
>>>>>>>> On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski <
>>>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>>> 
>>>>>>>>> The instructions even say the following:
>>>>>>>>> 
>>>>>>>>> If your secondary storage mount point is not named
>> /mnt/secondary,
>>>>>>>>> substitute your own mount point name.
>>>>>>>>> 
>>>>>>>>> On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski <
>>>>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>>>> 
>>>>>>>>>> Yeah, I've been through the instructions a couple times and don't
>>>>>>>>>> see anything that indicates why it's having trouble with /mnt/sec
>>> (it says
>>>>>>>>>> /mnt/sec instead of /mnt/secondary in the log messages).
>>>>>>>>>> 
>>>>>>>>>> On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal <
>>>>>>>>>> rsabh...@brocade.com> wrote:
>>>>>>>>>> 
>>>>>>>>>>> I have an external NFS server and it is mounted to
>> /mnt/secondary
>>>>>>>>>>> on my CS server so seeding command I used is:
>>>>>>>>>>> 
>>>>>>>>>>> 
>>> 
>> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>>>>>>>>>>> -m /mnt/secondary  -u
>>>>>>>>>>> 
>>> 
>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
>>>>>>>>>>> -h vmware -F
>>>>>>>>>>> 
>>>>>>>>>>> I guess, if the secondary storage is local, then
>> /export/secondary
>>>>>>>>>>> should be fine.
>>>>>>>>>>> 
>>>>>>>>>>> Regards,
>>>>>>>>>>> Ritu S.
>>>>>>>>>>> -Original Message-
>>>>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>>>>>>>>>>> Sent: Thursday, September 18, 2014 2:34 PM
>>>>>>>>>>> To: dev@cloudstack.apache.org
>>>>>>>>>>> Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty
>>>>>>>>>>> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up
>>> System
>>>>>>>>>>> VMs with Vmware setup with CS server
>>>>>>>>>>> 
>>>>>>>>>>> The instructions to seed secondary storage for VMware look like
>>>>>>>>>>> this:
>>>>>>>>>>> 
>>>>>>>>>>> 
>>> 
>> /usr/share/cloudstac

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

gt;>
> >>>>>>>private VirtualMachineDiskInfo
> >>>>>>> getMatchingExistingDisk(VirtualMachineDiskInfoBuilder
> >> diskInfoBuilder,
> >>>>>>> DiskTO vol) {
> >>>>>>>
> >>>>>>>if (diskInfoBuilder != null) {
> >>>>>>>
> >>>>>>>VolumeObjectTO volume = (VolumeObjectTO)vol.getData();
> >>>>>>>
> >>>>>>>String dsName =
> >>> volume.getDataStore().getUuid().replace("-",
> >>>>>>> "");
> >>>>>>>
> >>>>>>>
> >>>>>>> Map details = vol.getDetails();
> >>>>>>>
> >>>>>>>boolean isManaged = details != null &&
> >>>>>>> Boolean.parseBoolean(details.get(DiskTO.MANAGED));
> >>>>>>>
> >>>>>>>
> >>>>>>> VirtualMachineDiskInfo diskInfo =
> >>>>>>>
> >>>>>>>
> >>>>>>> diskInfoBuilder.getDiskInfoByBackingFileBaseName(isManaged ? new
> >>>>>>> DatastoreFile(volume.getPath()).getFileBaseName() :
> >> volume.getPath(),
> >>>>>>> dsName);
> >>>>>>>
> >>>>>>> On Thu, Sep 18, 2014 at 4:34 PM, Mike Tutkowski <
> >>>>>>> mike.tutkow...@solidfire.com> wrote:
> >>>>>>>
> >>>>>>>> I think I found the magic. :)
> >>>>>>>>
> >>>>>>>> sudo mount -t nfs 192.168.129.46:/export/secondary /mnt/sec
> >>>>>>>>
> >>>>>>>> If I mount /export/secondary to /mnt/sec (I did it in a bit of a
> >>>>>>>> roundabout way here), then the management server is happy.
> >>>>>>>>
> >>>>>>>> I think this is only VMware "thing" for the management server.
> >>>>>>>>
> >>>>>>>> Does anyone know if we document this?
> >>>>>>>>
> >>>>>>>> Thanks!
> >>>>>>>>
> >>>>>>>> On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski <
> >>>>>>>> mike.tutkow...@solidfire.com> wrote:
> >>>>>>>>
> >>>>>>>>> The instructions even say the following:
> >>>>>>>>>
> >>>>>>>>> If your secondary storage mount point is not named
> >> /mnt/secondary,
> >>>>>>>>> substitute your own mount point name.
> >>>>>>>>>
> >>>>>>>>> On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski <
> >>>>>>>>> mike.tutkow...@solidfire.com> wrote:
> >>>>>>>>>
> >>>>>>>>>> Yeah, I've been through the instructions a couple times and
> don't
> >>>>>>>>>> see anything that indicates why it's having trouble with
> /mnt/sec
> >>> (it says
> >>>>>>>>>> /mnt/sec instead of /mnt/secondary in the log messages).
> >>>>>>>>>>
> >>>>>>>>>> On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal <
> >>>>>>>>>> rsabh...@brocade.com> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> I have an external NFS server and it is mounted to
> >> /mnt/secondary
> >>>>>>>>>>> on my CS server so seeding command I used is:
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>
> >>
> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
> >>>>>>>>>>> -m /mnt/secondary  -u
> >>>>>>>>>>>
> >>>
> >>
> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
> >>>>>>>>>>> -h vmware -F
> >>>>>>>>>>>
> >>>>>>>>>>> I guess, if the secondary storage is local, then
> >> /export/secondary
> >>>>>>>>>>> 

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Abhinandan Prateek]

gt;>>> 
>>>>>>>>> The dsName is derived from the UUID of the datastore. This leads
>>>> to a
>>>>>>>>> null being returned from
>>>>> diskInfoBuilder.getDiskInfoByBackingFileBaseName,
>>>>>>>>> which subsequently leads to a null being returned from this method
>>>>> (and a
>>>>>>>>> NullPointerException being thrown).
>>>>>>>>> 
>>>>>>>>> I plan to take a look at the history of this file in gitk.
>>>>>>>>> 
>>>>>>>>>   private VirtualMachineDiskInfo
>>>>>>>>> getMatchingExistingDisk(VirtualMachineDiskInfoBuilder
>>>> diskInfoBuilder,
>>>>>>>>> DiskTO vol) {
>>>>>>>>> 
>>>>>>>>>   if (diskInfoBuilder != null) {
>>>>>>>>> 
>>>>>>>>>   VolumeObjectTO volume = (VolumeObjectTO)vol.getData();
>>>>>>>>> 
>>>>>>>>>   String dsName =
>>>>> volume.getDataStore().getUuid().replace("-",
>>>>>>>>> "");
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>Map details = vol.getDetails();
>>>>>>>>> 
>>>>>>>>>   boolean isManaged = details != null &&
>>>>>>>>> Boolean.parseBoolean(details.get(DiskTO.MANAGED));
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>VirtualMachineDiskInfo diskInfo =
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> diskInfoBuilder.getDiskInfoByBackingFileBaseName(isManaged ? new
>>>>>>>>> DatastoreFile(volume.getPath()).getFileBaseName() :
>>>> volume.getPath(),
>>>>>>>>> dsName);
>>>>>>>>> 
>>>>>>>>> On Thu, Sep 18, 2014 at 4:34 PM, Mike Tutkowski <
>>>>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>>>> 
>>>>>>>>>> I think I found the magic. :)
>>>>>>>>>> 
>>>>>>>>>> sudo mount -t nfs 192.168.129.46:/export/secondary /mnt/sec
>>>>>>>>>> 
>>>>>>>>>> If I mount /export/secondary to /mnt/sec (I did it in a bit of a
>>>>>>>>>> roundabout way here), then the management server is happy.
>>>>>>>>>> 
>>>>>>>>>> I think this is only VMware "thing" for the management server.
>>>>>>>>>> 
>>>>>>>>>> Does anyone know if we document this?
>>>>>>>>>> 
>>>>>>>>>> Thanks!
>>>>>>>>>> 
>>>>>>>>>> On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski <
>>>>>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>>>>> 
>>>>>>>>>>> The instructions even say the following:
>>>>>>>>>>> 
>>>>>>>>>>> If your secondary storage mount point is not named
>>>> /mnt/secondary,
>>>>>>>>>>> substitute your own mount point name.
>>>>>>>>>>> 
>>>>>>>>>>> On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski <
>>>>>>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>>>>>> 
>>>>>>>>>>>> Yeah, I've been through the instructions a couple times and
>> don't
>>>>>>>>>>>> see anything that indicates why it's having trouble with
>> /mnt/sec
>>>>> (it says
>>>>>>>>>>>> /mnt/sec instead of /mnt/secondary in the log messages).
>>>>>>>>>>>> 
>>>>>>>>>>>> On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal <
>>>>>>>>>>>> rsabh...@brocade.com> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>>> I have an external NFS server and it is mounted to
>>>> /mnt/s

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

> >>>> the
> >>>>>>>> DB.
> >>>>>>>>
> >>>>>>>> On Thu, Sep 18, 2014 at 5:12 PM, Mike Tutkowski <
> >>>>>>>> mike.tutkow...@solidfire.com> wrote:
> >>>>>>>>
> >>>>>>>>> Just a little update on this:
> >>>>>>>>>
> >>>>>>>>> The problem doesn't seem to have anything to do with "managed"
> >>>>>>>>> storage code that was introduced back in March.
> >>>>>>>>>
> >>>>>>>>> The dsName is derived from the UUID of the datastore. This leads
> >>>> to a
> >>>>>>>>> null being returned from
> >>>>> diskInfoBuilder.getDiskInfoByBackingFileBaseName,
> >>>>>>>>> which subsequently leads to a null being returned from this
> method
> >>>>> (and a
> >>>>>>>>> NullPointerException being thrown).
> >>>>>>>>>
> >>>>>>>>> I plan to take a look at the history of this file in gitk.
> >>>>>>>>>
> >>>>>>>>>   private VirtualMachineDiskInfo
> >>>>>>>>> getMatchingExistingDisk(VirtualMachineDiskInfoBuilder
> >>>> diskInfoBuilder,
> >>>>>>>>> DiskTO vol) {
> >>>>>>>>>
> >>>>>>>>>   if (diskInfoBuilder != null) {
> >>>>>>>>>
> >>>>>>>>>   VolumeObjectTO volume = (VolumeObjectTO)vol.getData();
> >>>>>>>>>
> >>>>>>>>>   String dsName =
> >>>>> volume.getDataStore().getUuid().replace("-",
> >>>>>>>>> "");
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>Map details = vol.getDetails();
> >>>>>>>>>
> >>>>>>>>>   boolean isManaged = details != null &&
> >>>>>>>>> Boolean.parseBoolean(details.get(DiskTO.MANAGED));
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>    VirtualMachineDiskInfo diskInfo =
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> diskInfoBuilder.getDiskInfoByBackingFileBaseName(isManaged ? new
> >>>>>>>>> DatastoreFile(volume.getPath()).getFileBaseName() :
> >>>> volume.getPath(),
> >>>>>>>>> dsName);
> >>>>>>>>>
> >>>>>>>>> On Thu, Sep 18, 2014 at 4:34 PM, Mike Tutkowski <
> >>>>>>>>> mike.tutkow...@solidfire.com> wrote:
> >>>>>>>>>
> >>>>>>>>>> I think I found the magic. :)
> >>>>>>>>>>
> >>>>>>>>>> sudo mount -t nfs 192.168.129.46:/export/secondary /mnt/sec
> >>>>>>>>>>
> >>>>>>>>>> If I mount /export/secondary to /mnt/sec (I did it in a bit of a
> >>>>>>>>>> roundabout way here), then the management server is happy.
> >>>>>>>>>>
> >>>>>>>>>> I think this is only VMware "thing" for the management server.
> >>>>>>>>>>
> >>>>>>>>>> Does anyone know if we document this?
> >>>>>>>>>>
> >>>>>>>>>> Thanks!
> >>>>>>>>>>
> >>>>>>>>>> On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski <
> >>>>>>>>>> mike.tutkow...@solidfire.com> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> The instructions even say the following:
> >>>>>>>>>>>
> >>>>>>>>>>> If your secondary storage mount point is not named
> >>>> /mnt/secondary,
> >>>>>>>>>>> substitute your own mount point name.
> >>>>>>>>>>>
> >>>>>>>>>>>

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Ian Duffy]

rtualMachineDiskInfo
> >>>>>>> getMatchingExistingDisk(VirtualMachineDiskInfoBuilder
> >> diskInfoBuilder,
> >>>>>>> DiskTO vol) {
> >>>>>>>
> >>>>>>>if (diskInfoBuilder != null) {
> >>>>>>>
> >>>>>>>VolumeObjectTO volume = (VolumeObjectTO)vol.getData();
> >>>>>>>
> >>>>>>>String dsName =
> >>> volume.getDataStore().getUuid().replace("-",
> >>>>>>> "");
> >>>>>>>
> >>>>>>>
> >>>>>>> Map details = vol.getDetails();
> >>>>>>>
> >>>>>>>boolean isManaged = details != null &&
> >>>>>>> Boolean.parseBoolean(details.get(DiskTO.MANAGED));
> >>>>>>>
> >>>>>>>
> >>>>>>> VirtualMachineDiskInfo diskInfo =
> >>>>>>>
> >>>>>>>
> >>>>>>> diskInfoBuilder.getDiskInfoByBackingFileBaseName(isManaged ? new
> >>>>>>> DatastoreFile(volume.getPath()).getFileBaseName() :
> >> volume.getPath(),
> >>>>>>> dsName);
> >>>>>>>
> >>>>>>> On Thu, Sep 18, 2014 at 4:34 PM, Mike Tutkowski <
> >>>>>>> mike.tutkow...@solidfire.com> wrote:
> >>>>>>>
> >>>>>>>> I think I found the magic. :)
> >>>>>>>>
> >>>>>>>> sudo mount -t nfs 192.168.129.46:/export/secondary /mnt/sec
> >>>>>>>>
> >>>>>>>> If I mount /export/secondary to /mnt/sec (I did it in a bit of a
> >>>>>>>> roundabout way here), then the management server is happy.
> >>>>>>>>
> >>>>>>>> I think this is only VMware "thing" for the management server.
> >>>>>>>>
> >>>>>>>> Does anyone know if we document this?
> >>>>>>>>
> >>>>>>>> Thanks!
> >>>>>>>>
> >>>>>>>> On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski <
> >>>>>>>> mike.tutkow...@solidfire.com> wrote:
> >>>>>>>>
> >>>>>>>>> The instructions even say the following:
> >>>>>>>>>
> >>>>>>>>> If your secondary storage mount point is not named
> >> /mnt/secondary,
> >>>>>>>>> substitute your own mount point name.
> >>>>>>>>>
> >>>>>>>>> On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski <
> >>>>>>>>> mike.tutkow...@solidfire.com> wrote:
> >>>>>>>>>
> >>>>>>>>>> Yeah, I've been through the instructions a couple times and
> don't
> >>>>>>>>>> see anything that indicates why it's having trouble with
> /mnt/sec
> >>> (it says
> >>>>>>>>>> /mnt/sec instead of /mnt/secondary in the log messages).
> >>>>>>>>>>
> >>>>>>>>>> On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal <
> >>>>>>>>>> rsabh...@brocade.com> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> I have an external NFS server and it is mounted to
> >> /mnt/secondary
> >>>>>>>>>>> on my CS server so seeding command I used is:
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>
> >>
> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
> >>>>>>>>>>> -m /mnt/secondary  -u
> >>>>>>>>>>>
> >>>
> >>
> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmware.ova
> >>>>>>>>>>> -h vmware -F
> >>>>>>>>>>>
> >>>>>>>>>>> I guess, if the secondary storage is local, then
> >> /export/secondary
> >>>>>>>>>>> should be fine.
> >>>>>

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Abhinandan Prateek]

The dsName is derived from the UUID of the datastore. This leads
>>>> to a
>>>>>>>>> null being returned from
>>>>> diskInfoBuilder.getDiskInfoByBackingFileBaseName,
>>>>>>>>> which subsequently leads to a null being returned from this method
>>>>> (and a
>>>>>>>>> NullPointerException being thrown).
>>>>>>>>> 
>>>>>>>>> I plan to take a look at the history of this file in gitk.
>>>>>>>>> 
>>>>>>>>>   private VirtualMachineDiskInfo
>>>>>>>>> getMatchingExistingDisk(VirtualMachineDiskInfoBuilder
>>>> diskInfoBuilder,
>>>>>>>>> DiskTO vol) {
>>>>>>>>> 
>>>>>>>>>   if (diskInfoBuilder != null) {
>>>>>>>>> 
>>>>>>>>>   VolumeObjectTO volume = (VolumeObjectTO)vol.getData();
>>>>>>>>> 
>>>>>>>>>   String dsName =
>>>>> volume.getDataStore().getUuid().replace("-",
>>>>>>>>> "");
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>Map details = vol.getDetails();
>>>>>>>>> 
>>>>>>>>>   boolean isManaged = details != null &&
>>>>>>>>> Boolean.parseBoolean(details.get(DiskTO.MANAGED));
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>VirtualMachineDiskInfo diskInfo =
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> diskInfoBuilder.getDiskInfoByBackingFileBaseName(isManaged ? new
>>>>>>>>> DatastoreFile(volume.getPath()).getFileBaseName() :
>>>> volume.getPath(),
>>>>>>>>> dsName);
>>>>>>>>> 
>>>>>>>>> On Thu, Sep 18, 2014 at 4:34 PM, Mike Tutkowski <
>>>>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>>>> 
>>>>>>>>>> I think I found the magic. :)
>>>>>>>>>> 
>>>>>>>>>> sudo mount -t nfs 192.168.129.46:/export/secondary /mnt/sec
>>>>>>>>>> 
>>>>>>>>>> If I mount /export/secondary to /mnt/sec (I did it in a bit of a
>>>>>>>>>> roundabout way here), then the management server is happy.
>>>>>>>>>> 
>>>>>>>>>> I think this is only VMware "thing" for the management server.
>>>>>>>>>> 
>>>>>>>>>> Does anyone know if we document this?
>>>>>>>>>> 
>>>>>>>>>> Thanks!
>>>>>>>>>> 
>>>>>>>>>> On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski <
>>>>>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>>>>> 
>>>>>>>>>>> The instructions even say the following:
>>>>>>>>>>> 
>>>>>>>>>>> If your secondary storage mount point is not named
>>>> /mnt/secondary,
>>>>>>>>>>> substitute your own mount point name.
>>>>>>>>>>> 
>>>>>>>>>>> On Thu, Sep 18, 2014 at 4:15 PM, Mike Tutkowski <
>>>>>>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>>>>>> 
>>>>>>>>>>>> Yeah, I've been through the instructions a couple times and
>> don't
>>>>>>>>>>>> see anything that indicates why it's having trouble with
>> /mnt/sec
>>>>> (it says
>>>>>>>>>>>> /mnt/sec instead of /mnt/secondary in the log messages).
>>>>>>>>>>>> 
>>>>>>>>>>>> On Thu, Sep 18, 2014 at 4:01 PM, Ritu Sabharwal <
>>>>>>>>>>>> rsabh...@brocade.com> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>>> I have an external NFS server and it is mounted to
>>>> /mnt/secondary
>>>>&

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

gt;>>> Little clarification on this:
> >>>>>>>>
> >>>>>>>> "The dsName is derived from the UUID of the datastore."
> >>>>>>>>
> >>>>>>>> I mean that the dsName is derived from the UUID primary storage in
> >>>> the
> >>>>>>>> DB.
> >>>>>>>>
> >>>>>>>> On Thu, Sep 18, 2014 at 5:12 PM, Mike Tutkowski <
> >>>>>>>> mike.tutkow...@solidfire.com> wrote:
> >>>>>>>>
> >>>>>>>>> Just a little update on this:
> >>>>>>>>>
> >>>>>>>>> The problem doesn't seem to have anything to do with "managed"
> >>>>>>>>> storage code that was introduced back in March.
> >>>>>>>>>
> >>>>>>>>> The dsName is derived from the UUID of the datastore. This leads
> >>>> to a
> >>>>>>>>> null being returned from
> >>>>> diskInfoBuilder.getDiskInfoByBackingFileBaseName,
> >>>>>>>>> which subsequently leads to a null being returned from this
> method
> >>>>> (and a
> >>>>>>>>> NullPointerException being thrown).
> >>>>>>>>>
> >>>>>>>>> I plan to take a look at the history of this file in gitk.
> >>>>>>>>>
> >>>>>>>>>   private VirtualMachineDiskInfo
> >>>>>>>>> getMatchingExistingDisk(VirtualMachineDiskInfoBuilder
> >>>> diskInfoBuilder,
> >>>>>>>>> DiskTO vol) {
> >>>>>>>>>
> >>>>>>>>>   if (diskInfoBuilder != null) {
> >>>>>>>>>
> >>>>>>>>>   VolumeObjectTO volume = (VolumeObjectTO)vol.getData();
> >>>>>>>>>
> >>>>>>>>>   String dsName =
> >>>>> volume.getDataStore().getUuid().replace("-",
> >>>>>>>>> "");
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>Map details = vol.getDetails();
> >>>>>>>>>
> >>>>>>>>>   boolean isManaged = details != null &&
> >>>>>>>>> Boolean.parseBoolean(details.get(DiskTO.MANAGED));
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>VirtualMachineDiskInfo diskInfo =
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> diskInfoBuilder.getDiskInfoByBackingFileBaseName(isManaged ? new
> >>>>>>>>> DatastoreFile(volume.getPath()).getFileBaseName() :
> >>>> volume.getPath(),
> >>>>>>>>> dsName);
> >>>>>>>>>
> >>>>>>>>> On Thu, Sep 18, 2014 at 4:34 PM, Mike Tutkowski <
> >>>>>>>>> mike.tutkow...@solidfire.com> wrote:
> >>>>>>>>>
> >>>>>>>>>> I think I found the magic. :)
> >>>>>>>>>>
> >>>>>>>>>> sudo mount -t nfs 192.168.129.46:/export/secondary /mnt/sec
> >>>>>>>>>>
> >>>>>>>>>> If I mount /export/secondary to /mnt/sec (I did it in a bit of a
> >>>>>>>>>> roundabout way here), then the management server is happy.
> >>>>>>>>>>
> >>>>>>>>>> I think this is only VMware "thing" for the management server.
> >>>>>>>>>>
> >>>>>>>>>> Does anyone know if we document this?
> >>>>>>>>>>
> >>>>>>>>>> Thanks!
> >>>>>>>>>>
> >>>>>>>>>> On Thu, Sep 18, 2014 at 4:18 PM, Mike Tutkowski <
> >>>>>>>>>> mike.tutkow...@solidfire.com> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> The instructions even say the following:
> >>>>>>>>>>>
> >>>>>&g

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Abhinandan Prateek]

;>>>>>>>> I think I know what the author was intending with the code that is
>>>>>>>>> causing the problem, so I'll go ahead and put in what I think is a
>>>>>> fix,
>>>>>>>>> re-create my env, and see if it works.
>>>>>>>>> 
>>>>>>>>> On Thu, Sep 18, 2014 at 6:26 PM, ilya musayev <
>>>> ilya.musa...@gmail.com
>>>>>>> 
>>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>>> Thank you Mike, please keep us posted.
>>>>>>>>>> 
>>>>>>>>>> Regards
>>>>>>>>>> ilya
>>>>>>>>>> 
>>>>>>>>>> On 9/18/14, 4:14 PM, Mike Tutkowski wrote:
>>>>>>>>>> 
>>>>>>>>>> Little clarification on this:
>>>>>>>>>> 
>>>>>>>>>> "The dsName is derived from the UUID of the datastore."
>>>>>>>>>> 
>>>>>>>>>> I mean that the dsName is derived from the UUID primary storage in
>>>>>> the
>>>>>>>>>> DB.
>>>>>>>>>> 
>>>>>>>>>> On Thu, Sep 18, 2014 at 5:12 PM, Mike Tutkowski <
>>>>>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>>>>> 
>>>>>>>>>>> Just a little update on this:
>>>>>>>>>>> 
>>>>>>>>>>> The problem doesn't seem to have anything to do with "managed"
>>>>>>>>>>> storage code that was introduced back in March.
>>>>>>>>>>> 
>>>>>>>>>>> The dsName is derived from the UUID of the datastore. This leads
>>>>>> to a
>>>>>>>>>>> null being returned from
>>>>>>> diskInfoBuilder.getDiskInfoByBackingFileBaseName,
>>>>>>>>>>> which subsequently leads to a null being returned from this
>> method
>>>>>>> (and a
>>>>>>>>>>> NullPointerException being thrown).
>>>>>>>>>>> 
>>>>>>>>>>> I plan to take a look at the history of this file in gitk.
>>>>>>>>>>> 
>>>>>>>>>>>  private VirtualMachineDiskInfo
>>>>>>>>>>> getMatchingExistingDisk(VirtualMachineDiskInfoBuilder
>>>>>> diskInfoBuilder,
>>>>>>>>>>> DiskTO vol) {
>>>>>>>>>>> 
>>>>>>>>>>>  if (diskInfoBuilder != null) {
>>>>>>>>>>> 
>>>>>>>>>>>  VolumeObjectTO volume = (VolumeObjectTO)vol.getData();
>>>>>>>>>>> 
>>>>>>>>>>>  String dsName =
>>>>>>> volume.getDataStore().getUuid().replace("-",
>>>>>>>>>>> "");
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>>   Map details = vol.getDetails();
>>>>>>>>>>> 
>>>>>>>>>>>  boolean isManaged = details != null &&
>>>>>>>>>>> Boolean.parseBoolean(details.get(DiskTO.MANAGED));
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>>   VirtualMachineDiskInfo diskInfo =
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> diskInfoBuilder.getDiskInfoByBackingFileBaseName(isManaged ? new
>>>>>>>>>>> DatastoreFile(volume.getPath()).getFileBaseName() :
>>>>>> volume.getPath(),
>>>>>>>>>>> dsName);
>>>>>>>>>>> 
>>>>>>>>>>> On Thu, Sep 18, 2014 at 4:34 PM, Mike Tutkowski <
>>>>>>>>>>> mike.tutkow...@solidfire.com> wrote:
>>>>>>>>>>> 
>>>>>>>>>>>> I think I found the magic. :)
>>>>>>>>>>>

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

t;>>>>>
> >>>>>>>> I don't personally know a whole lot about how the virtual router
> >> code
> >>>>>>>> works, so we should pass that on to an appropriate developer.
> >>>>>>>>
> >>>>>>>> On Thu, Sep 18, 2014 at 6:35 PM, Mike Tutkowski <
> >>>>>>>> mike.tutkow...@solidfire.com> wrote:
> >>>>>>>>
> >>>>>>>>> Just destroyed and re-created my env from scratch without
> >>>>>>>>> 8bb4022f3729154f85036c4a7f55e2de783e4909 and it works fine.
> >>>>>>>>>
> >>>>>>>>> I think I know what the author was intending with the code that
> is
> >>>>>>>>> causing the problem, so I'll go ahead and put in what I think is
> a
> >>>>>> fix,
> >>>>>>>>> re-create my env, and see if it works.
> >>>>>>>>>
> >>>>>>>>> On Thu, Sep 18, 2014 at 6:26 PM, ilya musayev <
> >>>> ilya.musa...@gmail.com
> >>>>>>>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> Thank you Mike, please keep us posted.
> >>>>>>>>>>
> >>>>>>>>>> Regards
> >>>>>>>>>> ilya
> >>>>>>>>>>
> >>>>>>>>>> On 9/18/14, 4:14 PM, Mike Tutkowski wrote:
> >>>>>>>>>>
> >>>>>>>>>> Little clarification on this:
> >>>>>>>>>>
> >>>>>>>>>> "The dsName is derived from the UUID of the datastore."
> >>>>>>>>>>
> >>>>>>>>>> I mean that the dsName is derived from the UUID primary storage
> in
> >>>>>> the
> >>>>>>>>>> DB.
> >>>>>>>>>>
> >>>>>>>>>> On Thu, Sep 18, 2014 at 5:12 PM, Mike Tutkowski <
> >>>>>>>>>> mike.tutkow...@solidfire.com> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> Just a little update on this:
> >>>>>>>>>>>
> >>>>>>>>>>> The problem doesn't seem to have anything to do with "managed"
> >>>>>>>>>>> storage code that was introduced back in March.
> >>>>>>>>>>>
> >>>>>>>>>>> The dsName is derived from the UUID of the datastore. This
> leads
> >>>>>> to a
> >>>>>>>>>>> null being returned from
> >>>>>>> diskInfoBuilder.getDiskInfoByBackingFileBaseName,
> >>>>>>>>>>> which subsequently leads to a null being returned from this
> >> method
> >>>>>>> (and a
> >>>>>>>>>>> NullPointerException being thrown).
> >>>>>>>>>>>
> >>>>>>>>>>> I plan to take a look at the history of this file in gitk.
> >>>>>>>>>>>
> >>>>>>>>>>>  private VirtualMachineDiskInfo
> >>>>>>>>>>> getMatchingExistingDisk(VirtualMachineDiskInfoBuilder
> >>>>>> diskInfoBuilder,
> >>>>>>>>>>> DiskTO vol) {
> >>>>>>>>>>>
> >>>>>>>>>>>  if (diskInfoBuilder != null) {
> >>>>>>>>>>>
> >>>>>>>>>>>      VolumeObjectTO volume = (VolumeObjectTO)vol.getData();
> >>>>>>>>>>>
> >>>>>>>>>>>  String dsName =
> >>>>>>> volume.getDataStore().getUuid().replace("-",
> >>>>>>>>>>> "");
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>   Map details = vol.getDetails();
> >>>>>>>>>>>
> >>>>>>>>>>>  boolean isManaged = details != null &&
> >>>>>>>>&g

RE: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Sateesh Chodapuneedi]

> -Original Message-
> From: Abhinandan Prateek [mailto:agneya2...@gmail.com]
> Sent: 22 September 2014 10:29
> To: CloudStack Dev
> Cc: Sateesh Chodapuneedi
> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with 
> Vmware setup with CS server
> 
> Mike,
> 
>   Lets wait for sometime, till someone from Citrix respond.
> I am working from Garage and not from Citrix and do not have quick access to 
> VMWare setup.
> In case we are still not sure about the VMWare template then we can plan a 
> more collaborative effort by participating in a debugging
> session.
> I can pass on the information on issues that I have seen, we can then put 
> some joint effort to fix these followed by
> documenting/automating these.
> 
> I still hope that Sateesh or someone form Citrix respond on the latex VMware 
> templates and procedure.
> 
> -abhi
> 
> On 21-Sep-2014, at 3:57 am, Mike Tutkowski  
> wrote:
> 
> > So, I just tried with this system template and got (essentially) the
> > same results.
> >
> > I say "essentially" because with this template I never arrived at a
> > login prompt (it just shut down at some point in the boot stage). With
> > the other template, I was brought to the login prompt and then the VM was 
> > shut down.
> >
> > On Fri, Sep 19, 2014 at 9:18 PM, Abhinandan Prateek
> > 
> > wrote:
> >
> >>
> >> VMWare Template:
> >> http://download.cloud.com/templates/4.5/systemvm64template-4.5-vmware
> >> .ova
> >> Checksum: 3106a79a4ce66cd7f6a7c50e93f2db57

I am running ACS master with this template without issues.
Can somebody file a JIRA ticket and attach all relevant logs? I will check it.
May be patching of systemvm is not working in the setup where VR did not come 
up. 

For information aboutman manual changes to Jenkins generated templates, please 
see ACS tickets CLOUDSTACK-5883 
(https://issues.apache.org/jira/browse/CLOUDSTACK-5883?focusedCommentId=13906809&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13906809)
And CLOUDSTACK-4864.

Regards,
Sateesh

> >>
> >> Last I checked systemvm.iso will not get mounted.
> >>
> >> -abhi
> >>
> >> On 20-Sep-2014, at 8:32 am, Mike Tutkowski
> >> 
> >> wrote:
> >>
> >>> Can you provide me a link to the Citrix ones?
> >>>
> >>> Does this mean the standard build for VMware on Jenkins in terms of
> >>> the system template is pretty much useless when it comes to the
> >>> virtual
> >> router?
> >>>
> >>> Thanks
> >>>
> >>> On Fri, Sep 19, 2014 at 7:49 PM, Abhinandan Prateek <
> >> agneya2...@gmail.com>
> >>> wrote:
> >>>
> >>>> The VMWare template build by jenkins job does not have VMWare tools
> >>>> installed on it.
> >>>> Use the ones provided by Citrix.
> >>>>
> >>>> On 19-Sep-2014, at 9:31 pm, Mike Tutkowski <
> >> mike.tutkow...@solidfire.com>
> >>>> wrote:
> >>>>
> >>>>>
> >>>>
> >> http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSucces
> >> sfulBuild/artifact/tools/appliance/dist/systemvm64template-master-vmw
> >> are.ova
> >>>>>
> >>>>> On Fri, Sep 19, 2014 at 9:58 AM, Erik Weber 
> >> wrote:
> >>>>>
> >>>>>> Which systemvm template are you using?
> >>>>>>
> >>>>>> Erik
> >>>>>> 19. sep. 2014 03:47 skrev "Mike Tutkowski" <
> >>>> mike.tutkow...@solidfire.com>
> >>>>>> følgende:
> >>>>>>
> >>>>>>> Actually, the virtual router says it requires an upgrade.
> >>>>>>>
> >>>>>>> I think I can just turn that check off and re-run my create-VM test.
> >>>>>>>
> >>>>>>> On Thu, Sep 18, 2014 at 7:43 PM, Mike Tutkowski <
> >>>>>>> mike.tutkow...@solidfire.com> wrote:
> >>>>>>>
> >>>>>>>> OK, I checked in a fix for this:
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>
> >> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff
> >> ;h=18e5aa116e99906f24a292bf75

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

I opened the following ticket:

https://issues.apache.org/jira/browse/CLOUDSTACK-7599

Where can I put vmops.log? It's about 14MB and 10MB is JIRA's attachment
limit.

On Mon, Sep 22, 2014 at 9:21 AM, Sateesh Chodapuneedi <
sateesh.chodapune...@citrix.com> wrote:

> > -Original Message-
> > From: Abhinandan Prateek [mailto:agneya2...@gmail.com]
> > Sent: 22 September 2014 10:29
> > To: CloudStack Dev
> > Cc: Sateesh Chodapuneedi
> > Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs
> with Vmware setup with CS server
> >
> > Mike,
> >
> >   Lets wait for sometime, till someone from Citrix respond.
> > I am working from Garage and not from Citrix and do not have quick
> access to VMWare setup.
> > In case we are still not sure about the VMWare template then we can plan
> a more collaborative effort by participating in a debugging
> > session.
> > I can pass on the information on issues that I have seen, we can then
> put some joint effort to fix these followed by
> > documenting/automating these.
> >
> > I still hope that Sateesh or someone form Citrix respond on the latex
> VMware templates and procedure.
> >
> > -abhi
> >
> > On 21-Sep-2014, at 3:57 am, Mike Tutkowski 
> wrote:
> >
> > > So, I just tried with this system template and got (essentially) the
> > > same results.
> > >
> > > I say "essentially" because with this template I never arrived at a
> > > login prompt (it just shut down at some point in the boot stage). With
> > > the other template, I was brought to the login prompt and then the VM
> was shut down.
> > >
> > > On Fri, Sep 19, 2014 at 9:18 PM, Abhinandan Prateek
> > > 
> > > wrote:
> > >
> > >>
> > >> VMWare Template:
> > >> http://download.cloud.com/templates/4.5/systemvm64template-4.5-vmware
> > >> .ova
> > >> Checksum: 3106a79a4ce66cd7f6a7c50e93f2db57
>
> I am running ACS master with this template without issues.
> Can somebody file a JIRA ticket and attach all relevant logs? I will check
> it.
> May be patching of systemvm is not working in the setup where VR did not
> come up.
>
> For information aboutman manual changes to Jenkins generated templates,
> please see ACS tickets CLOUDSTACK-5883 (
> https://issues.apache.org/jira/browse/CLOUDSTACK-5883?focusedCommentId=13906809&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13906809
> )
> And CLOUDSTACK-4864.
>
> Regards,
> Sateesh
>
> > >>
> > >> Last I checked systemvm.iso will not get mounted.
> > >>
> > >> -abhi
> > >>
> > >> On 20-Sep-2014, at 8:32 am, Mike Tutkowski
> > >> 
> > >> wrote:
> > >>
> > >>> Can you provide me a link to the Citrix ones?
> > >>>
> > >>> Does this mean the standard build for VMware on Jenkins in terms of
> > >>> the system template is pretty much useless when it comes to the
> > >>> virtual
> > >> router?
> > >>>
> > >>> Thanks
> > >>>
> > >>> On Fri, Sep 19, 2014 at 7:49 PM, Abhinandan Prateek <
> > >> agneya2...@gmail.com>
> > >>> wrote:
> > >>>
> > >>>> The VMWare template build by jenkins job does not have VMWare tools
> > >>>> installed on it.
> > >>>> Use the ones provided by Citrix.
> > >>>>
> > >>>> On 19-Sep-2014, at 9:31 pm, Mike Tutkowski <
> > >> mike.tutkow...@solidfire.com>
> > >>>> wrote:
> > >>>>
> > >>>>>
> > >>>>
> > >> http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSucces
> > >> sfulBuild/artifact/tools/appliance/dist/systemvm64template-master-vmw
> > >> are.ova
> > >>>>>
> > >>>>> On Fri, Sep 19, 2014 at 9:58 AM, Erik Weber 
> > >> wrote:
> > >>>>>
> > >>>>>> Which systemvm template are you using?
> > >>>>>>
> > >>>>>> Erik
> > >>>>>> 19. sep. 2014 03:47 skrev "Mike Tutkowski" <
> > >>>> mike.tutkow...@solidfire.com>
> > >>>>>> følgende:
> > >>>>>>
> > >>>>>>> Actually, the virtual router says it requires an upgrade.

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

I just updated the ticket with an FYI that the 4.4 system template (which I
just tried) with CS 4.4 worked fine for the SSVM, CPVM, and the virtual
router.

On Mon, Sep 22, 2014 at 10:57 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> I opened the following ticket:
>
> https://issues.apache.org/jira/browse/CLOUDSTACK-7599
>
> Where can I put vmops.log? It's about 14MB and 10MB is JIRA's attachment
> limit.
>
> On Mon, Sep 22, 2014 at 9:21 AM, Sateesh Chodapuneedi <
> sateesh.chodapune...@citrix.com> wrote:
>
>> > -Original Message-
>> > From: Abhinandan Prateek [mailto:agneya2...@gmail.com]
>> > Sent: 22 September 2014 10:29
>> > To: CloudStack Dev
>> > Cc: Sateesh Chodapuneedi
>> > Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs
>> with Vmware setup with CS server
>> >
>> > Mike,
>> >
>> >   Lets wait for sometime, till someone from Citrix respond.
>> > I am working from Garage and not from Citrix and do not have quick
>> access to VMWare setup.
>> > In case we are still not sure about the VMWare template then we can
>> plan a more collaborative effort by participating in a debugging
>> > session.
>> > I can pass on the information on issues that I have seen, we can then
>> put some joint effort to fix these followed by
>> > documenting/automating these.
>> >
>> > I still hope that Sateesh or someone form Citrix respond on the latex
>> VMware templates and procedure.
>> >
>> > -abhi
>> >
>> > On 21-Sep-2014, at 3:57 am, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>> >
>> > > So, I just tried with this system template and got (essentially) the
>> > > same results.
>> > >
>> > > I say "essentially" because with this template I never arrived at a
>> > > login prompt (it just shut down at some point in the boot stage). With
>> > > the other template, I was brought to the login prompt and then the VM
>> was shut down.
>> > >
>> > > On Fri, Sep 19, 2014 at 9:18 PM, Abhinandan Prateek
>> > > 
>> > > wrote:
>> > >
>> > >>
>> > >> VMWare Template:
>> > >>
>> http://download.cloud.com/templates/4.5/systemvm64template-4.5-vmware
>> > >> .ova
>> > >> Checksum: 3106a79a4ce66cd7f6a7c50e93f2db57
>>
>> I am running ACS master with this template without issues.
>> Can somebody file a JIRA ticket and attach all relevant logs? I will
>> check it.
>> May be patching of systemvm is not working in the setup where VR did not
>> come up.
>>
>> For information aboutman manual changes to Jenkins generated templates,
>> please see ACS tickets CLOUDSTACK-5883 (
>> https://issues.apache.org/jira/browse/CLOUDSTACK-5883?focusedCommentId=13906809&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13906809
>> )
>> And CLOUDSTACK-4864.
>>
>> Regards,
>> Sateesh
>>
>> > >>
>> > >> Last I checked systemvm.iso will not get mounted.
>> > >>
>> > >> -abhi
>> > >>
>> > >> On 20-Sep-2014, at 8:32 am, Mike Tutkowski
>> > >> 
>> > >> wrote:
>> > >>
>> > >>> Can you provide me a link to the Citrix ones?
>> > >>>
>> > >>> Does this mean the standard build for VMware on Jenkins in terms of
>> > >>> the system template is pretty much useless when it comes to the
>> > >>> virtual
>> > >> router?
>> > >>>
>> > >>> Thanks
>> > >>>
>> > >>> On Fri, Sep 19, 2014 at 7:49 PM, Abhinandan Prateek <
>> > >> agneya2...@gmail.com>
>> > >>> wrote:
>> > >>>
>> > >>>> The VMWare template build by jenkins job does not have VMWare tools
>> > >>>> installed on it.
>> > >>>> Use the ones provided by Citrix.
>> > >>>>
>> > >>>> On 19-Sep-2014, at 9:31 pm, Mike Tutkowski <
>> > >> mike.tutkow...@solidfire.com>
>> > >>>> wrote:
>> > >>>>
>> > >>>>>
>> > >>>>
>> > >>
>> http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSucces
>> > >> sfulBuild/artifact/tools/a

RE: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Ritu Sabharwal]

Hi Mike,

From where did you use the system vm template for 4.4 case?

Thanks & Regards,
Ritu S.

-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Monday, September 22, 2014 12:19 PM
To: dev@cloudstack.apache.org
Cc: Abhinandan Prateek
Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with 
Vmware setup with CS server

I just updated the ticket with an FYI that the 4.4 system template (which I 
just tried) with CS 4.4 worked fine for the SSVM, CPVM, and the virtual router.

On Mon, Sep 22, 2014 at 10:57 AM, Mike Tutkowski < 
mike.tutkow...@solidfire.com> wrote:

> I opened the following ticket:
>
> https://issues.apache.org/jira/browse/CLOUDSTACK-7599
>
> Where can I put vmops.log? It's about 14MB and 10MB is JIRA's
> attachment limit.
>
> On Mon, Sep 22, 2014 at 9:21 AM, Sateesh Chodapuneedi <
> sateesh.chodapune...@citrix.com> wrote:
>
>> > -Original Message-
>> > From: Abhinandan Prateek [mailto:agneya2...@gmail.com]
>> > Sent: 22 September 2014 10:29
>> > To: CloudStack Dev
>> > Cc: Sateesh Chodapuneedi
>> > Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System
>> > VMs
>> with Vmware setup with CS server
>> >
>> > Mike,
>> >
>> >   Lets wait for sometime, till someone from Citrix respond.
>> > I am working from Garage and not from Citrix and do not have quick
>> access to VMWare setup.
>> > In case we are still not sure about the VMWare template then we can
>> plan a more collaborative effort by participating in a debugging
>> > session.
>> > I can pass on the information on issues that I have seen, we can
>> > then
>> put some joint effort to fix these followed by
>> > documenting/automating these.
>> >
>> > I still hope that Sateesh or someone form Citrix respond on the
>> > latex
>> VMware templates and procedure.
>> >
>> > -abhi
>> >
>> > On 21-Sep-2014, at 3:57 am, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>> >
>> > > So, I just tried with this system template and got (essentially)
>> > > the same results.
>> > >
>> > > I say "essentially" because with this template I never arrived at
>> > > a login prompt (it just shut down at some point in the boot
>> > > stage). With the other template, I was brought to the login
>> > > prompt and then the VM
>> was shut down.
>> > >
>> > > On Fri, Sep 19, 2014 at 9:18 PM, Abhinandan Prateek
>> > > 
>> > > wrote:
>> > >
>> > >>
>> > >> VMWare Template:
>> > >>
>> http://download.cloud.com/templates/4.5/systemvm64template-4.5-vmware
>> > >> .ova
>> > >> Checksum: 3106a79a4ce66cd7f6a7c50e93f2db57
>>
>> I am running ACS master with this template without issues.
>> Can somebody file a JIRA ticket and attach all relevant logs? I will
>> check it.
>> May be patching of systemvm is not working in the setup where VR did
>> not come up.
>>
>> For information aboutman manual changes to Jenkins generated
>> templates, please see ACS tickets CLOUDSTACK-5883 (
>> https://issues.apache.org/jira/browse/CLOUDSTACK-5883?focusedCommentI
>> d=13906809&page=com.atlassian.jira.plugin.system.issuetabpanels:comme
>> nt-tabpanel#comment-13906809
>> )
>> And CLOUDSTACK-4864.
>>
>> Regards,
>> Sateesh
>>
>> > >>
>> > >> Last I checked systemvm.iso will not get mounted.
>> > >>
>> > >> -abhi
>> > >>
>> > >> On 20-Sep-2014, at 8:32 am, Mike Tutkowski
>> > >> 
>> > >> wrote:
>> > >>
>> > >>> Can you provide me a link to the Citrix ones?
>> > >>>
>> > >>> Does this mean the standard build for VMware on Jenkins in
>> > >>> terms of the system template is pretty much useless when it
>> > >>> comes to the virtual
>> > >> router?
>> > >>>
>> > >>> Thanks
>> > >>>
>> > >>> On Fri, Sep 19, 2014 at 7:49 PM, Abhinandan Prateek <
>> > >> agneya2...@gmail.com>
>> > >>> wrote:
>> > >>>
>> > >>>> The VMWare template build by jenkins job does not have VMWare
>> > >>>

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-4.4-2014-09-22-vmware.ova

On Mon, Sep 22, 2014 at 1:58 PM, Ritu Sabharwal 
wrote:

> Hi Mike,
>
> From where did you use the system vm template for 4.4 case?
>
> Thanks & Regards,
> Ritu S.
>
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Monday, September 22, 2014 12:19 PM
> To: dev@cloudstack.apache.org
> Cc: Abhinandan Prateek
> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs
> with Vmware setup with CS server
>
> I just updated the ticket with an FYI that the 4.4 system template (which
> I just tried) with CS 4.4 worked fine for the SSVM, CPVM, and the virtual
> router.
>
> On Mon, Sep 22, 2014 at 10:57 AM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
> > I opened the following ticket:
> >
> > https://issues.apache.org/jira/browse/CLOUDSTACK-7599
> >
> > Where can I put vmops.log? It's about 14MB and 10MB is JIRA's
> > attachment limit.
> >
> > On Mon, Sep 22, 2014 at 9:21 AM, Sateesh Chodapuneedi <
> > sateesh.chodapune...@citrix.com> wrote:
> >
> >> > -Original Message-
> >> > From: Abhinandan Prateek [mailto:agneya2...@gmail.com]
> >> > Sent: 22 September 2014 10:29
> >> > To: CloudStack Dev
> >> > Cc: Sateesh Chodapuneedi
> >> > Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System
> >> > VMs
> >> with Vmware setup with CS server
> >> >
> >> > Mike,
> >> >
> >> >   Lets wait for sometime, till someone from Citrix respond.
> >> > I am working from Garage and not from Citrix and do not have quick
> >> access to VMWare setup.
> >> > In case we are still not sure about the VMWare template then we can
> >> plan a more collaborative effort by participating in a debugging
> >> > session.
> >> > I can pass on the information on issues that I have seen, we can
> >> > then
> >> put some joint effort to fix these followed by
> >> > documenting/automating these.
> >> >
> >> > I still hope that Sateesh or someone form Citrix respond on the
> >> > latex
> >> VMware templates and procedure.
> >> >
> >> > -abhi
> >> >
> >> > On 21-Sep-2014, at 3:57 am, Mike Tutkowski <
> >> mike.tutkow...@solidfire.com> wrote:
> >> >
> >> > > So, I just tried with this system template and got (essentially)
> >> > > the same results.
> >> > >
> >> > > I say "essentially" because with this template I never arrived at
> >> > > a login prompt (it just shut down at some point in the boot
> >> > > stage). With the other template, I was brought to the login
> >> > > prompt and then the VM
> >> was shut down.
> >> > >
> >> > > On Fri, Sep 19, 2014 at 9:18 PM, Abhinandan Prateek
> >> > > 
> >> > > wrote:
> >> > >
> >> > >>
> >> > >> VMWare Template:
> >> > >>
> >> http://download.cloud.com/templates/4.5/systemvm64template-4.5-vmware
> >> > >> .ova
> >> > >> Checksum: 3106a79a4ce66cd7f6a7c50e93f2db57
> >>
> >> I am running ACS master with this template without issues.
> >> Can somebody file a JIRA ticket and attach all relevant logs? I will
> >> check it.
> >> May be patching of systemvm is not working in the setup where VR did
> >> not come up.
> >>
> >> For information aboutman manual changes to Jenkins generated
> >> templates, please see ACS tickets CLOUDSTACK-5883 (
> >> https://issues.apache.org/jira/browse/CLOUDSTACK-5883?focusedCommentI
> >> d=13906809&page=com.atlassian.jira.plugin.system.issuetabpanels:comme
> >> nt-tabpanel#comment-13906809
> >> )
> >> And CLOUDSTACK-4864.
> >>
> >> Regards,
> >> Sateesh
> >>
> >> > >>
> >> > >> Last I checked systemvm.iso will not get mounted.
> >> > >>
> >> > >> -abhi
> >> > >>
> >> > >> On 20-Sep-2014, at 8:32 am, Mike Tutkowski
> >> > >> 
> >> > >> wrote:
> >> > >>
> >> > >>> Can you provide me a li

Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server

[Mike Tutkowski]

I just put that info in the ticket, too.

On Mon, Sep 22, 2014 at 2:04 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

>
> http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-4.4-2014-09-22-vmware.ova
>
> On Mon, Sep 22, 2014 at 1:58 PM, Ritu Sabharwal 
> wrote:
>
>> Hi Mike,
>>
>> From where did you use the system vm template for 4.4 case?
>>
>> Thanks & Regards,
>> Ritu S.
>>
>> -Original Message-
>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> Sent: Monday, September 22, 2014 12:19 PM
>> To: dev@cloudstack.apache.org
>> Cc: Abhinandan Prateek
>> Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs
>> with Vmware setup with CS server
>>
>> I just updated the ticket with an FYI that the 4.4 system template (which
>> I just tried) with CS 4.4 worked fine for the SSVM, CPVM, and the virtual
>> router.
>>
>> On Mon, Sep 22, 2014 at 10:57 AM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>> > I opened the following ticket:
>> >
>> > https://issues.apache.org/jira/browse/CLOUDSTACK-7599
>> >
>> > Where can I put vmops.log? It's about 14MB and 10MB is JIRA's
>> > attachment limit.
>> >
>> > On Mon, Sep 22, 2014 at 9:21 AM, Sateesh Chodapuneedi <
>> > sateesh.chodapune...@citrix.com> wrote:
>> >
>> >> > -Original Message-
>> >> > From: Abhinandan Prateek [mailto:agneya2...@gmail.com]
>> >> > Sent: 22 September 2014 10:29
>> >> > To: CloudStack Dev
>> >> > Cc: Sateesh Chodapuneedi
>> >> > Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System
>> >> > VMs
>> >> with Vmware setup with CS server
>> >> >
>> >> > Mike,
>> >> >
>> >> >   Lets wait for sometime, till someone from Citrix respond.
>> >> > I am working from Garage and not from Citrix and do not have quick
>> >> access to VMWare setup.
>> >> > In case we are still not sure about the VMWare template then we can
>> >> plan a more collaborative effort by participating in a debugging
>> >> > session.
>> >> > I can pass on the information on issues that I have seen, we can
>> >> > then
>> >> put some joint effort to fix these followed by
>> >> > documenting/automating these.
>> >> >
>> >> > I still hope that Sateesh or someone form Citrix respond on the
>> >> > latex
>> >> VMware templates and procedure.
>> >> >
>> >> > -abhi
>> >> >
>> >> > On 21-Sep-2014, at 3:57 am, Mike Tutkowski <
>> >> mike.tutkow...@solidfire.com> wrote:
>> >> >
>> >> > > So, I just tried with this system template and got (essentially)
>> >> > > the same results.
>> >> > >
>> >> > > I say "essentially" because with this template I never arrived at
>> >> > > a login prompt (it just shut down at some point in the boot
>> >> > > stage). With the other template, I was brought to the login
>> >> > > prompt and then the VM
>> >> was shut down.
>> >> > >
>> >> > > On Fri, Sep 19, 2014 at 9:18 PM, Abhinandan Prateek
>> >> > > 
>> >> > > wrote:
>> >> > >
>> >> > >>
>> >> > >> VMWare Template:
>> >> > >>
>> >> http://download.cloud.com/templates/4.5/systemvm64template-4.5-vmware
>> >> > >> .ova
>> >> > >> Checksum: 3106a79a4ce66cd7f6a7c50e93f2db57
>> >>
>> >> I am running ACS master with this template without issues.
>> >> Can somebody file a JIRA ticket and attach all relevant logs? I will
>> >> check it.
>> >> May be patching of systemvm is not working in the setup where VR did
>> >> not come up.
>> >>
>> >> For information aboutman manual changes to Jenkins generated
>> >> templates, please see ACS tickets CLOUDSTACK-5883 (
>> >> https://issues.apache.org/jira/browse/CLOUDSTACK-5883?focusedCommentI
>> >> d=13906809&page=com.atlassian.jira.plugin.system.issuetabpanels:comme
>> >> nt-tabpanel#comment-13906809