Machine costs in vRA are not reflecting with the costs associated in vRB
search cancel

Machine costs in vRA are not reflecting with the costs associated in vRB

book

Article ID: 314928

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:

Machine costs represented in vRealize Automation does not show up properly or match that of vRealize Business.
 
This issue may occur due when:
  • Reconfigured machine do not display correct cost according to its new configuration.
  • Deployment running cost does not account for deleted machines (scale in, scale out, destroy) and destroyed machines.
  • Machine Cost per day may not be in sync with vRealize Business when costing policy is updated.
  • Imported machines do not have the cost displayed correctly after data collection by vRealize Business.
  • After a bulk import of virtual machines into vRealize Automation, running a cost calculation shows Cost to Date column of Items tab a 0 value.
  • In facts-repo.log file, you see entries similar to:

    2016-07-15 16:21:30.506 WARN [qtp469623948-17] o.e.j.s.HttpChannel - /snapshot/requests/system/<UUID>
    java.lang.OutOfMemoryError: Java heap space
    2016-07-15 16:21:30.508 WARN [qtp469623948-36] o.e.j.u.t.QueuedThreadPool - Unexpected thread death:     org.eclipse.jetty.util.thread.QueuedThreadPool$3@29a00473 in [FAILED toString()]
    2016-07-15 16:21:30.509 WARN [qtp469623948-17] o.e.j.s.HttpChannel - Could not send response error 500: java.lang.OutOfMemoryError: Java heap space
    2016-07-15 16:21:33.218 WARN [qtp469623948-17] o.e.j.h.HttpParser - badMessage: 400 No Host for     HttpChannelOverHttp@10afa1ee{r=0,c=false,a=IDLE,uri=/metrics/ping }
    2016-07-15 16:21:37.513 ERROR [qtp469623948-18] c.v.v.f.i.ChangesInputController - Failure responding to request: /input/changes/system
    java.lang.OutOfMemoryError: Java heap space
    2016-07-15 16:21:30.508 ERROR [qtp469623948-37] c.v.v.f.i.ChangesInputController - Parsing the request body failed, because:
    java.lang.OutOfMemoryError: Java heap space
    at java.nio.HeapByteBuffer.<init>(HeapByteBuffer.java:57) ~[?:1.7.0_95]
    at java.nio.ByteBuffer.allocate(ByteBuffer.java:331) ~[?:1.7.0_95]

     
  • In itfm-server.log, you see entries similar to:

    2016-07-15 16:20:13.562 ERROR [SystemSync] c.v.i.c.c.s.j.SystemSynchronizationManager - Job SYSTEM_SYNCHRONIZATION Failed.
    com.vmware.itfm.cloud.sync.input.inventory.factsrepo.framework.FactsRepoClientException: Failed executing HTTP request: Request{method=GET, url=http://localhost:8088/snapshot/requests/system/<UUID>, tag=null}
    at com.vmware.itfm.cloud.sync.input.inventory.factsrepo.FactsRepoHttpClient.executeCall(FactsRepoHttpClient.java:100) ~[itfm-common-utils-7.0.1.0.jar:7.0.1.0]
    at com.vmware.itfm.cloud.sync.input.inventory.factsrepo.FactsRepoHttpClient.executeCall(FactsRepoHttpClient.java:74) ~[itfm-common-utils-7.0.1.0.jar:7.0.1.0]
    at com.vmware.itfm.cloud.sync.input.inventory.factsrepo.service.SnapshotService.pollAndCheck(SnapshotService.java:151) ~[itfm-sync-7.0.1.0.jar:7.0.1.0]
    at com.vmware.itfm.cloud.sync.input.inventory.factsrepo.service.SnapshotService.access$100(SnapshotService.java:46) ~[itfm-sync-7.0.1.0.jar:7.0.1.0]
    at com.vmware.itfm.cloud.sync.input.inventory.factsrepo.service.SnapshotService$SnapshotStatusPollingTask.run(SnapshotService.java:277) [itfm-sync-7.0.1.0.jar:7.0.1.0]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [?:1.7.0_95]
    at java.util.concurrent.FutureTask.run(FutureTask.java:262) [?:1.7.0_95]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) [?:1.7.0_95]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) [?:1.7.0_95]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [?:1.7.0_95]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [?:1.7.0_95]
    at java.lang.Thread.run(Thread.java:745) [?:1.7.0_95]
    Caused by: java.io.InterruptedIOException: timeout

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

 

Environment

VMware vRealize Automation 7.2.x
VMware vRealize Automation 7.1.x
VMware vRealize Automation 7.0.x

Cause

The cost field within vRealize Automation is a static field within the database. It is updated only when the virtual machine is provisioned. VMs which are imported do not include the cost data so it is not updated.

Resolution

This is a known issue affecting VMware vRealize Automation 7.1.

These issues are fixed in VMware vRealize Automation 7.3 release.


Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box.

Powered by Wolken Software