Comment 6 for bug 1839181

Hi Yang,
What does below sentence mean?
"This alarm is reproduced only when lock/unlock on controller executed prior to this test case."

I cannot reproduce the issue with my 2+2+2 VM environment. I try to lock/unlock compute/storage/controller node.

From attached log, except dpdk process, it seems there is no other process consumed too much CPU per /var/extra/process.info log. So I guess when the alarm occur, it is just a spike/jitter, and will be cleared later. Is it right?
Could you help login to the compute node to check which process consume the CPU when issue occur?
Thanks.