IBM Support

PH04653: Updated CPU limit (--cpus) not recognized by usage metering feature

Fixes are available

18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a Docker container is first started without specifying
    the --cpus option to limit CPU resources, and later a Docker
    update is performed that does limit CPU resources, the
    Virtual Processor Cores value reported by the usage metering
    feature does not reflect the update. The value displayed on
    the IBM Cloud Private metering service dashboard remains the
    same, and is the total number of processors available on the
    hardware or virtual machine.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty- Usage Metering              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Updated CPU limit (--cpus) not          *
    *                      recognized by usage metering feature    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If a Docker container is first started without specifying the --
    cpus option to limit CPU resources, and later a Docker update is
    performed that does limit CPU resources, the Virtual Processor
    Cores value reported by the usage metering feature does not
    reflect the update. The value displayed on the IBM Cloud Private
    metering service dashboard remains the same, and is the total
    number of processors available on the hardware or virtual
    machine.
    

Problem conclusion

  • The usage metering feature has been updated to check for CPU
    limit updates every usage report interval for containers,
    regardless if an initial limit was provided.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 18.0.0.4 for WebSphere Application Server Liberty and
    9.0.0.11 and 8.5.5.15 for WebSphere Application Server.  Please
    refer to the Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH04653

  • Reported component name

    WAS LIBERTY COR

  • Reported component ID

    5725L2900

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-10-29

  • Closed date

    2018-11-05

  • Last modified date

    2018-11-05

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WAS LIBERTY COR

  • Fixed component ID

    5725L2900

Applicable component levels

  • RCD0 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 October 2021