Comment 0 for bug 1839181

Brief Description
-----------------
Platform CPU threshold exceeded 95% during compute node lock & unlock in a storage system. This is reproduced multiple times in daily sanity.

Severity
--------
Provide the severity of the defect.
Critical: The compute remain in the degraded state after unlock

Steps to Reproduce
------------------
1. system host-lock compute
2. system host-unlock compute

This alarm is reproduced only when lock/unlock on controller executed prior to this test case.

Expected Behavior
------------------
The compute expected to be unlocked and in the available state with no alarm raised for CPU threshold.

Actual Behavior
----------------
| Platform CPU threshold exceeded; threshold 95.00%, actual 99.99%

Reproducibility
---------------
CPU threshold issue is reproduced multiple times in daily sanity. Also seen in load 201907290421.

System Configuration
--------------------
Storage System

Branch/Pull Time/Commit
-----------------------
20190804T233000Z

Last Pass
---------
20190728T013000Z

Timestamp/Logs
--------------
====================== Test Step 2: Lock compute host - compute-0 and ensure it is successfully locked
[2019-08-05 08:30:30,888] 301 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.144.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-endpoint-type internalURL --os-region-name RegionOne host-lock compute-0'
====================== Test Step 3: Unlock compute host - compute-0 and ensure it is successfully unlocked
[2019-08-05 08:31:15,904] 301 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.144.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-endpoint-type internalURL --os-region-name RegionOne host-unlock compute-0'

Test Activity
-------------
Sanity