Re: Login hangs/freezes after update to 4.9.2.0

[Rohit Yadav]

Martin,


While performing upgrades, did you upgrade in-place or setup a new management 
server (installed fresh rpms)?


If you had installed mgmt server on a new server (freshly installed), did you 
copy the commands.properties and other files from old mgmt server's 
/etc/cloudstack?


I would advise enabling dynamic roles, please see this: 
http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.9/accounts.html#using-dynamic-roles


Regards.


From: Martin Emrich 
Sent: 27 January 2017 14:57:50
To: users@cloudstack.apache.org
Subject: Login hangs/freezes after update to 4.9.2.0

Hi!

I just updated my test system from 4.7.0 to 4.9.2.0... Now I cannot login 
anymore: The web UI completely freezes after clicking the login button.
(It freezes so hard, I have to kill the management server process before I can 
even close the tab in the browser).

Cloudmonkey also hangs after issuing a command.

The only line I see in the log after clicking "login":

2017-01-27 10:26:14,920 DEBUG [c.c.a.ApiServlet] (catalina-exec-2:ctx-e6b0a361) 
(logid:e9cfda72) ===START===  10.14.2.6 -- POST

An Idea where I could start digging?

Thanks

Martin


rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: Upgrade 4.7 to 4.9 issue

[Cloud List]

Hi Yuriy, Simon and all,

Apologies for digging out an old thread. We were hit by this bug when we
tried to upgrade to 4.9.0 some time in Nov 2016 -- all our KVM agents were
not able to start with similar error messages as outlined on this thread,
so we had to upgrade to 4.8.1 instead.

May I know if the latest ACS 4.9.2 fixes this bug? I can't seem to find the
associated JIRA article for the bug.

Looking forward to your reply, thank you.

Cheers.


On Thu, Sep 8, 2016 at 3:37 PM, Yuriy Karpel  wrote:

> Sorry for the long answer. I updated to 4.8.1 there is no problem.
>
> 2016-08-16 22:34 GMT+03:00 Simon Weller :
>
> > This is interesting. So, at a cursory glance, it seems that your
> interface
> > name for the private.network.device is causing a problem with 4.9.
> >
> > Do you have a lab environment where you could change the private network
> > interface to see what happens?
> >
> >
> > You might want to try an update to 4.8.1 and see whether the issue exists
> > there.
> >
> >
> > - si
> >
> > 
> > From: Yuriy Karpel 
> > Sent: Tuesday, August 16, 2016 2:05 PM
> > To: users@cloudstack.apache.org
> > Subject: Re: Upgrade 4.7 to 4.9 issue
> >
> > [root@srv-kvm01 ~]# cat /etc/cloudstack/agent/agent.properties
> > #Storage
> > #Tue Aug 16 19:57:54 MSK 2016
> > guest.network.device=cloudbr0
> > workers=5
> > private.network.device=mgm0
> > port=8250
> > resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
> > guest.cpu.mode=IvyBridge
> > pod=4
> > zone=4
> > guid=49e79980-b27f-377f-835f-8686d83f971f
> > hypervisor.type=kvm
> > cluster=4
> > public.network.device=cloudbr0
> > local.storage.uuid=16b92fae-597c-4f5c-a560-400e041232c3
> > domr.scripts.dir=scripts/network/domr/kvm
> > host=10.30.10.42
> > LibvirtComputingResource.id=121
> >
> >
> > 2016-08-16 20:17 GMT+03:00 Simon Weller :
> >
> > > Can you post your agent.properties file?
> > >
> > >
> > > 
> > > From: Yuriy Karpel 
> > > Sent: Tuesday, August 16, 2016 11:53 AM
> > > To: users@cloudstack.apache.org
> > > Subject: Re: Upgrade 4.7 to 4.9 issue
> > >
> > > 2016-08-16 19:50:22,861 INFO  [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Agent started
> > > 2016-08-16 19:50:22,865 INFO  [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Implementation Version is 4.9.0
> > > 2016-08-16 19:50:22,867 INFO  [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > agent.properties found at /etc/cloudstack/agent/agent.properties
> > > 2016-08-16 19:50:22,873 DEBUG [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Found property: guest.network.device
> > > 2016-08-16 19:50:22,873 DEBUG [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Found property: workers
> > > 2016-08-16 19:50:22,873 DEBUG [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Found property: private.network.device
> > > 2016-08-16 19:50:22,873 DEBUG [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Found property: port
> > > 2016-08-16 19:50:22,873 DEBUG [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Found property: resource
> > > 2016-08-16 19:50:22,873 DEBUG [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Found property: guest.cpu.mode
> > > 2016-08-16 19:50:22,873 DEBUG [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Found property: pod
> > > 2016-08-16 19:50:22,874 DEBUG [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Found property: zone
> > > 2016-08-16 19:50:22,874 DEBUG [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Found property: hypervisor.type
> > > 2016-08-16 19:50:22,874 DEBUG [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Found property: guid
> > > 2016-08-16 19:50:22,874 DEBUG [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Found property: public.network.device
> > > 2016-08-16 19:50:22,874 DEBUG [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Found property: cluster
> > > 2016-08-16 19:50:22,874 DEBUG [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Found property: local.storage.uuid
> > > 2016-08-16 19:50:22,874 DEBUG [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Found property: domr.scripts.dir
> > > 2016-08-16 19:50:22,874 DEBUG [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Found property: LibvirtComputingResource.id
> > > 2016-08-16 19:50:22,874 DEBUG [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Found property: host
> > > 2016-08-16 19:50:22,875 INFO  [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Defaulting to using properties file for storage
> > > 2016-08-16 19:50:22,876 INFO  [cloud.agent.AgentShell] (main:null)
> > (logid:)
> > > Defaulting to the constant time backoff algorithm
> > > 2016-08-16 19:50:22,895 INFO  [cloud.utils.LogUtils] (main:null)
> (logid:)
> > > log4j configuration found at /etc/cloudstack/agent/log4j-cloud.xml
> > > 2016-08-16 

Re: cs 4.5.1, vm stopped when putting xen hosts in maintenance

[Rafael Weingärtner]

This seems to be one of those nasty bugs that are very hard to debug. It
seems to be cause to a combination of different factors, such as planets
alignments ;)

At class “VirtualMachineManagerImpl” line 2395 (method
“com.cloud.vm.VirtualMachineManagerImpl.orchestrateMigrateAway(String,
long, DeploymentPlanner)”) is the start of the code flow that triggers the
migration. The point here is that, if an error occurs during the migration,
the VM will be stopped; For some reason this is executed only for HA VMs.

Going a little bit further, we find the point that is triggering the error
in the method “com.cloud.vm.VirtualMachineManagerImpl.migrate(VMInstanceVO,
long, DeployDestination)” at line 1941. This line will call the method
“com.cloud.vm.VirtualMachineManagerImpl.changeState(VMInstanceVO, Event,
Long, ItWorkVO, Step)” to change the VM state to migrating/prepare
migration/or something like that (I am guessing here), but for some reason,
the state of the VM is not the one expected and this is causing a
“ConcurrentOperationException” to be thrown. The problem is that the
“com.cloud.vm.VirtualMachineManagerImpl.changeState(VMInstanceVO, Event,
Long, ItWorkVO, Step)” does not seem to provide much useful log entries.

Just to enable us to discuss the problem a little further, could you tell
us a little bit about your environment setting? How many ACS MSs do you
have? What is the VM workload being migrated (I mean, the number of VMs and
computing resources)? Do the other servers have enough computing resources
to support these VMs? Could you also check the XenServer logs, and check
what happened on both, source and destination hosts when the migration for
VM “i-638-1735-VM” was triggered?

Do you have the knowledge/skills to use an IDE (e.g. Eclipse) to connect to
a running JVM and debug a code? Because for me it will not be possible to
go further without looking at the variables in a running environment.


On Mon, Jan 30, 2017 at 4:28 AM, Francois Scheurer <
francois.scheu...@everyware.ch> wrote:

> Dear Rafael
>
>
> Sorry for the late answer (was sick a couple of days).
>
> I confirm we are migrating inside the same xenserver pool (within a CS
> Cluster).
>
>
> Best Regards
> Francois
>
>
>
> On 26.01.2017 04:35, Rafael Weingärtner wrote:
>
>> Found the code that is executed.
>> I need you to confirm if you are migrating within a cluster or across
>> clusters?
>>
>> On Wed, Jan 25, 2017 at 11:57 AM, Rafael Weingärtner <
>> rafaelweingart...@gmail.com> wrote:
>>
>> I do not have access to ACS code right now, but I suggest starting
>>> debugging here:
>>>
>>> 2017-01-24 18:05:28,427 DEBUG [c.c.c.CapacityManagerImpl]
 (Work-Job-Executor-156:ctx-14b86f5e job-60216/job-191380 ctx-175d37df)
 VM state transitted from :Running to Stopping with event:
 StopRequestedvm's
 original host id: 224 new host id: 15 host id before state transition:
 15

 I would try to understand first why ACS requested the hypervisor to stop
>>> the VM. I mean the following, check the source code for conditions that
>>> would make ACS request the shutdown of VMs.
>>> BTW: are you migrating within a cluster or across clusters?
>>>
>>> I will be able to analyze this further only after work hours, so if you
>>> find anything, keep me posted.
>>>
>>> On Wed, Jan 25, 2017 at 11:45 AM, Francois Scheurer <
>>> francois.scheu...@everyware.ch> wrote:
>>>
>>> Hello Rafael


 I think the important log lines are these:

 ewcstack-man02-prod: 2017-01-24 18:05:28,407 INFO
 [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-156:ctx-14b86f5e
 job-60216/job-191380 ctx-175d37df) Migration cancelled because state has
 changed: VM[User|i-638-1736-VM]
 ewcstack-man02-prod: 2017-01-24 18:05:28,407 DEBUG
 [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-156:ctx-14b86f5e
 job-60216/job-191380 ctx-175d37df) Unable to migrate VM due to:
 Migration
 cancelled because state has changed: VM[User|i-638-1736-VM]
 ewcstack-man02-prod: 2017-01-24 18:05:28,427 DEBUG
 [c.c.c.CapacityManagerImpl] (Work-Job-Executor-156:ctx-14b86f5e
 job-60216/job-191380 ctx-175d37df) VM state transitted from :Running to
 Stopping with event: StopRequestedvm's original host id: 224 new host
 id:
 15 host id before state transition: 15

 The really disturbing thing is that CS stop again the VM if we start it
 manually, apparently because the migratingjob is still running.

 Note the the VM HA Flag is enabled.



 Thank you.


 Best Regards.

 Francois






 more details:



 ewcstack-man02-prod: 2017-01-24 18:05:28,148 DEBUG
 [o.a.c.e.o.VolumeOrchestrator] (Work-Job-Executor-156:ctx-14b86f5e
 job-60216/job-191380 ctx-175d37df) Preparing 3 volumes for
 VM[User|i-638-1736-VM]
 ewcstack-man02-prod: 2017-01-24 18:05:28,155 DEBUG
 [c.c.v.VmWorkJobDispatcher] 

Re: CCC Miami Update

[Wido den Hollander]

> Op 29 januari 2017 om 19:41 schreef Will Stevens :
> 
> 
> Hello Everyone,
> I am sure most of you are aware at this point that a CloudStack
> Collaboration Conference (CCC) is being hosted in Miami on May 16-18 by
> ApacheCon.
> 
> I urge you to consider joining us at this event.  Here are some of the
> important event details, but all the details can be found on our event
> website: *http://us.cloudstackcollab.org/ *
> 
> *Deadline for talk submissions:* *February 11th, 2017*
> *Accepted talk notifications:* *March 6th, 2017*
> *Schedule published on: **March 9th, 2017*
> 
> The event is being run as a collection of independently themed
> conferences.  Obviously, most of you will be specifically interested in the
> CloudStack Collaboration Conference, but your registration also gives you
> access to the other conference being run at the same time.  So far the
> other conferences include; 'Apache: Big Data', 'Apache: IoT', 'Flex Project
> Summit', 'Apache Traffic Server / Apache Traffic Control' and 'TomcatCon'.
> 
> The earlier you register, the more you save, so get your registration in
> early.
> 
> *Early Registration:* *until March 12, 2017*
> *Standard Registration:* *March 13, 2017 - April 16, 2017*
> *Late Registration:* *April 17, 2017 - Event Date*
> *Committer Registration:* Special pricing is available for active Apache
> Committers. Please contact the event organizers 
> for details.
> *Speaker Registration:* *One free registration is included with each
> accepted talk.*
> 
> If you submit a talk  and
> your talk is accepted, you will get one free registration per talk accepted.
> 

Great! With the recent merge of the IPv6 code for KVM Basic Networking I 
submitted a talk for IPv6 in Basic Networking.

This means I will be flying over to Miami in May :)

Wido

> We are still looking for event sponsors, so if you are interested in
> sponsoring the event, please review the sponsorship details
> .
> 
> If you have questions about anything, feel free to contact me directly and
> I will make sure you are connected with the right people.
> 
> Looking forward to seeing you all in Miami.
> 
> Cheers,
> 
> Will

Re: developing own webinterface

[Michels, Thorsten]

Hi Swen,

I think, this is quite an effort to take, to build a new GUI for CS. But
sometimes it is worthwhile.

Our colleagues from the DEV team, made some very good experiences with
JavaScript as a language to implement GUIs. It is quite easy to learn
and powerfull to use.

But, as always, it depends. It depends on the tools the user will use to
access the GUI. If it is a web-browser, one has to take care of the
little compatibility problems here and there, which may become some kind
of a nightmare. If people are not using a web-browser, you may think of
a (thin-)client implemented in Java, .NET, or any other language to use
some graphical frameworks.

It has shown, that web-GUIs accessed via a web-browser are the most
common approach and with the great frameworks in JS available, it is not
really rocket-science to implement a nice looking GUI.

I hope this does help you somehow further.


Cheers

Thorsten


Am 30.01.2017 um 11:43 schrieb S. Brüseke - proIO GmbH:
> Hello,
>
> we want to develop our own webinterface for CS and I want to ask if somebody 
> also did this in the past and can share the experience. Our webinterface will 
> use API calls, but what language is the best to use for a webinterface? We 
> use PHP a lot for our web projects, but I am not use if this is the best 
> option here, because sometimes you need a runtime to fulfill a chain of API 
> calls with unknown outcome.
>
> Can you please share your experience? Thx!
>
> Mit freundlichen Grüßen / With kind regards,
>
> Swen
>
>
>
>
> - proIO GmbH -
> Geschäftsführer: Swen Brüseke
> Sitz der Gesellschaft: Frankfurt am Main
>
> USt-IdNr. DE 267 075 918
> Registergericht: Frankfurt am Main - HRB 86239
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
> Informationen. 
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
> erhalten haben, 
> informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
> Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
> gestattet. 
>
> This e-mail may contain confidential and/or privileged information. 
> If you are not the intended recipient (or have received this e-mail in error) 
> please notify 
> the sender immediately and destroy this e-mail.  
> Any unauthorized copying, disclosure or distribution of the material in this 
> e-mail is strictly forbidden. 
>
>

Re: developing own webinterface

[Rene Moser]

Hi Swen

I have plans to develop a new UI for CloudStack in this year, which will
be most likely be implemented with vue.js https://vuejs.org/.

Regards
René

developing own webinterface

[S . Brüseke - proIO GmbH]

Hello,

we want to develop our own webinterface for CS and I want to ask if somebody 
also did this in the past and can share the experience. Our webinterface will 
use API calls, but what language is the best to use for a webinterface? We use 
PHP a lot for our web projects, but I am not use if this is the best option 
here, because sometimes you need a runtime to fulfill a chain of API calls with 
unknown outcome.

Can you please share your experience? Thx!

Mit freundlichen Grüßen / With kind regards,

Swen




- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, 
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet. 

This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient (or have received this e-mail in error) 
please notify 
the sender immediately and destroy this e-mail.  
Any unauthorized copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden. 

Re: cs 4.5.1, vm stopped when putting xen hosts in maintenance

[Francois Scheurer]

Dear Rafael


Sorry for the late answer (was sick a couple of days).

I confirm we are migrating inside the same xenserver pool (within a CS 
Cluster).



Best Regards
Francois


On 26.01.2017 04:35, Rafael Weingärtner wrote:

Found the code that is executed.
I need you to confirm if you are migrating within a cluster or across
clusters?

On Wed, Jan 25, 2017 at 11:57 AM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:


I do not have access to ACS code right now, but I suggest starting
debugging here:


2017-01-24 18:05:28,427 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-156:ctx-14b86f5e job-60216/job-191380 ctx-175d37df)
VM state transitted from :Running to Stopping with event: StopRequestedvm's
original host id: 224 new host id: 15 host id before state transition: 15


I would try to understand first why ACS requested the hypervisor to stop
the VM. I mean the following, check the source code for conditions that
would make ACS request the shutdown of VMs.
BTW: are you migrating within a cluster or across clusters?

I will be able to analyze this further only after work hours, so if you
find anything, keep me posted.

On Wed, Jan 25, 2017 at 11:45 AM, Francois Scheurer <
francois.scheu...@everyware.ch> wrote:


Hello Rafael


I think the important log lines are these:

ewcstack-man02-prod: 2017-01-24 18:05:28,407 INFO
[c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-156:ctx-14b86f5e
job-60216/job-191380 ctx-175d37df) Migration cancelled because state has
changed: VM[User|i-638-1736-VM]
ewcstack-man02-prod: 2017-01-24 18:05:28,407 DEBUG
[c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-156:ctx-14b86f5e
job-60216/job-191380 ctx-175d37df) Unable to migrate VM due to: Migration
cancelled because state has changed: VM[User|i-638-1736-VM]
ewcstack-man02-prod: 2017-01-24 18:05:28,427 DEBUG
[c.c.c.CapacityManagerImpl] (Work-Job-Executor-156:ctx-14b86f5e
job-60216/job-191380 ctx-175d37df) VM state transitted from :Running to
Stopping with event: StopRequestedvm's original host id: 224 new host id:
15 host id before state transition: 15

The really disturbing thing is that CS stop again the VM if we start it
manually, apparently because the migratingjob is still running.

Note the the VM HA Flag is enabled.



Thank you.


Best Regards.

Francois






more details:



ewcstack-man02-prod: 2017-01-24 18:05:28,148 DEBUG
[o.a.c.e.o.VolumeOrchestrator] (Work-Job-Executor-156:ctx-14b86f5e
job-60216/job-191380 ctx-175d37df) Preparing 3 volumes for
VM[User|i-638-1736-VM]
ewcstack-man02-prod: 2017-01-24 18:05:28,155 DEBUG
[c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-122:ctx-a8bacc64
job-14953/job-191351) Done with run of VM work job:
com.cloud.vm.VmWorkMigrateAway for VM 1411, job origin: 14953
ewcstack-man02-prod: 2017-01-24 18:05:28,155 DEBUG
[o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-122:ctx-a8bacc64
job-14953/job-191351) Done executing com.cloud.vm.VmWorkMigrateAway for
job-191351
ewcstack-man02-prod: 2017-01-24 18:05:28,160 INFO
[o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-122:ctx-a8bacc64
job-14953/job-191351) Remove job-191351 from job monitoring
ewcstack-man02-prod: 2017-01-24 18:05:28,168 INFO
[c.c.h.HighAvailabilityManagerImpl] (HA-Worker-2:ctx-f3bcf43c work-1989)
Completed HAWork[1989-Migration-1411-Running-Migrating]
ewcstack-man02-prod: 2017-01-24 18:05:28,246 DEBUG
[c.c.a.m.ClusteredAgentAttache] (Work-Job-Executor-156:ctx-14b86f5e
job-60216/job-191380 ctx-175d37df) Seq 19-8526158519542516375: Forwarding
Seq 19-8526158519542516375:  { Cmd , MgmtId: 345049103441, via:
19(ewcstack-vh010-prod), Ver: v1, Flags: 100111, [{
"com.cloud.agent.api.PrepareForMigrationCommand":{"vm":{"id"
:1736,"name":"i-638-1736-VM","bootloader":"PyGrub","type":"U
ser","cpus":4,"minSpeed":2100,"maxSpeed":2100,"minRam":17179
869184,"maxRam":17179869184,"arch":"x86_64","os":"Other
(64-bit)","platformEmulator":"Other install media","bootArgs":"","enable
HA":true,"limitCpuUse":true,"enableDynamicallyScaleVm":true,
"vncPassword":"pC1WUC7h1DBH9J36q3H9pg==","params":{"memoryOv
ercommitRatio":"1.0","platform":"viridian:true;acpi:1;apic:t
rue;pae:true;nx:true;timeoffset:-3601","keyboard":"us","Mess
age.ReservedCapacityFreed.Flag":"false","cpuOvercommitRatio":"4.0","
hypervisortoolsversion":"xenserver61"},"uuid":"5bff01de-c033
-4925-9e47-30dd14539272","disks":[{"data":{"org.apache.cloud
stack.storage.to.VolumeObjectTO":{"uuid":"1ab514b2-f2de-
4d85-8e0d-9768184a1349","volumeType":"ROOT","dataStore":{"org.
apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"b8751b89-00f
6-5079-ed7a-c073579c7563","id":64,"poolType":"PreSetup","hos
t":"localhost","path":"/b8751b89-00f6-5079-ed7a-c073579c7563
","port":0,"url":"PreSetup://localhost/b8751b89-00f6-5079-ed
7a-c073579c7563/?ROLE=Primary=b8751b89-00f6-5079-
ed7a-c073579c7563"}},"name":"ROOT-1736","size":53687091200,"path":"d3
f87e3c-1efe-42ad-aa93-609d5b980a34","volumeId":8655,"vmName"
:"i-638-1736-VM","accountId":638,"format":"VHD","provisionin