Search Engine: Elastic

Article ID: 132096, created on Jan 19, 2018, last review on Jan 19, 2018

  • Applies to:
  • Operations Automation 7.1

Symptoms

Customer ordered OACI VPS with 1024 MB of RAM, but subscription in OA was created with Limit of 1000 MB of RAM. On BA side, customer ordered 2 items of 512MB "PACI Memory" resource.

According to core.log, RAM resource limit as sent to OA like below:

c.p.p.s.s.e.SubscriptionResourcesManagerBean validating subscription #*** resource type #1002294 limit 1024000

Why real RAM size does not correspond with ordered?

Cause

Incorrectly set Unit of Measure for Megabytes of RAM on BA side.

Resolution

Resource UoM for RAM is a megabyte (MB), which uses kilobyte (KB) as a base resource. Correct multiplier in this case is 1024.

Before sending resource limits to OA, BA converts them to base unit of measure. If multiplier for MB UoM is incorrectly set to 1000, then 1024000 KB will be sent, which is effectively 1024000 KB / 1024 = 1000 MB.

In order to fix the discrepancy, set multiplier for megabytes to 1024 (default value).

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 8c199f0ee4305da1a577740620df4a51 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF