Search Engine: Elastic

Article ID: 133962, created on Apr 25, 2019, last review on Apr 25, 2019

  • Applies to:
  • Operations Automation 8.0
  • Operations Automation 7.4


  1. CPU Core Power resource unit of measure was changed from MHzh to GHzh.
  2. The CS virtual server template is configured with a relatively small step for Core Power (e.g. 100 MHz).
  3. When pressing 'Add new server' button on the Cloud Servers screen in UX1, the calculated fee for CPU Power shows unexpected values like: $0.0/2.431432432e-16 GHz per month.


A cosmetic software issue CCU-20167.


To show correct human-readable values, 2 workarounds are possible:

  1. Switch back to MHzh.
  2. Configure CPU Power with a 500 MHz or 1 GHz step.

adc6deaa66054d8a194d131ba07f2785 8fc71f07abe5b233fea1ae0377cd5e3d 5356b422f65bdad1c3e9edca5d74a1ae aab95f5cf9bcfa920cc1dda8487f084a 55fe109b4b4fe3fbb893f22dbb85a41a 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF