[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16684579#comment-16684579
 ] 

ASF subversion and git services commented on CLOUDSTACK-3009:
-------------------------------------------------------------

Commit f6e600e4d8134dd317ec8444ccf259285932dd50 in cloudstack's branch 
refs/heads/4.11 from Bitworks LLC
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=f6e600e ]

CLOUDSTACK-3009: Fix resource calculation CPU, RAM for accounts. (#3012)

The view "service_offering_view" doesn't include removed SOs, as a result when 
SO is removed, the bug happens. The PR introduces a change for resource 
calculation changing "service_offering_view" to "service_offering" table which 
has all service offerings.

Must be fixed in:

4.12
4.11
Fixes: #3009

> [VPC][VMware]Unable to execute NetworkUsage command on DomR (10.147.40.181), 
> domR may not be ready yet. failure due to Exception: java.lang.Exception—when 
> VPC/VPC VR is rebooted
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3009
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3009
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Network Controller
>    Affects Versions: 4.2.0
>            Reporter: manasaveloori
>            Assignee: Kishan Kavala
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: management-server.zip
>
>
> Steps:
> 1.    Have a CS with advanced zone and with VMware host.
> 2.    Create VPC .
> 3.    Create a private gateway and a static route to it.
> 4.    Reboot  the VPC VR.
> 5.    After successful reboot of VR, now restart the VPC.
>            OR
> After step 3 Restart the VPC and after successful restart, now reboot VR.
> Observation:
> Observed the following exception when VPC is restarted/VR is rebooted.
> 2013-06-14 20:11:28,390 ERROR [vmware.resource.VmwareResource] 
> (DirectAgent-142:10.147.40.29) Unable to execute NetworkUsage command on DomR 
> (10.147.40.184), domR may not be ready yet. failure due to Exception: 
> java.lang.Exception
> Message:  vpc network usage get returns empty
> java.lang.Exception:  vpc network usage get returns empty
>         at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.VPCNetworkUsage(VmwareResource.java:676)
>         at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:622)
>         at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:472)
>         at 
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
>         at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>         at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
>         at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
>         at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:679)
> 2013-06-14 20:11:28,400 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-142:null) Seq 1-519307624: Response Received:
> Attaching the MS log.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to