There is a memory leak bug in Pmon alarm

[YeHuiSheng]

When the system launch pmond process, it will malloc memory which is pointed by a temporary variable "alarm_list_ptr" in function "manage_queried_alarms".
However, there is no list or free function called in "manage_queried_alarms".
When the function "manage_queried_alarms" is finished, the temporary variable "alarm_list_ptr" will be unusable.
Then the memory must be leaked.

Fortunately,the function "manage_queried_alarms" will be called only once in the pmond.
So, it will waste only a little memory.

[Ghada Khalil (gkhalil)]

Low priority / not gating - would be nice to fix as it is related to a memory leak, but likely the leak is small and doesn't cause any negative system impact

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/670012
Committed: https://git.openstack.org/cgit/starlingx/metal/commit/?id=7875130a80aa2b1df3ddd769bde1f68aabe4c392
Submitter: Zuul
Branch: master

commit 7875130a80aa2b1df3ddd769bde1f68aabe4c392
Author: YeHuiSheng <email address hidden>
Date: Wed Jul 10 16:19:06 2019 +0800

    Modify a memory leak bug in Pmon alarm.

    Add a free call after malloc in the Pmon alarm module.

    Change-Id: I2ca948f28959e1b99f19777410b2f906b27a3e2e
    Closes-Bug: #1836130
    Signed-off-by: YeHuiSheng <email address hidden>