I was thinking that, i'll be out enjoying the sun, nightynight
On Sat, Aug 8, 2015 at 11:39 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> It would seem so. :)
>
> Well, it's almost 4 AM here...time for bed.
>
> On Sat, Aug 8, 2015 at 3:34 AM, Daan Hoogland
> wrote:
>
> > so a PR wi
It would seem so. :)
Well, it's almost 4 AM here...time for bed.
On Sat, Aug 8, 2015 at 3:34 AM, Daan Hoogland
wrote:
> so a PR with only a log statement following? ;>
>
> On Sat, Aug 8, 2015 at 11:26 AM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
> > OK, just to close this "issu
so a PR with only a log statement following? ;>
On Sat, Aug 8, 2015 at 11:26 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> OK, just to close this "issue" out:
>
> It turns out I forgot to mount my /export/secondary to /mnt/sec. Simple as
> that. :) Unfortunately the error messages I
OK, just to close this "issue" out:
It turns out I forgot to mount my /export/secondary to /mnt/sec. Simple as
that. :) Unfortunately the error messages I was receiving didn't really
indicate anything like that.
Also, I was able to easily re-route the CopyCommand so I could debug it via
Eclipse i
Is there an easy way to avoid routing this command to the SSVM so that I
can debug the code in Eclipse more easily?
For example, VMwareGuru is where we decide to route this command to the
SSVM.
Would it be OK if I went in via the debugger and had it not route to the
SSVM, so the CopyCommand would
Here's some relevant text from the cloud.log file on the SSVM. It, too,
indicates an UnsupportedAnswer exception.
2015-08-08 08:37:26,657 DEBUG [cloud.agent.Agent]
(agentRequest-Handler-3:null) Request:Seq 4-2159476021324152902: { Cmd ,
MgmtId: 52237617797, via: 4, Ver: v1, Flags: 100111,
[{"org.
I had a little time to look into this and here's what I found so far:
An UnsupportedAnswer exception is being returned by the secondary storage
VM when the CopyCommand is sent to it to copy the template from secondary
to primary storage.
Perhaps unrelated, but I also noticed in the host_details t
