"proposed_repair_action" attribute is not visible in WRCP /var/log/fm-event.log

[Fabrizio Perez]

Brief Description
-----------------
Is necessary to aggregate all fm events to central system controller from each subclouds.

These fm-event will be consumed by external tool for fault management.

Problem: comparing SNMP attributes and output from these tools and notice they are different each other, since one fm-event.log doesn't provide 'proposed_repair_action' even when it is available from event show.

Provide the severity of the defect.

Severity
--------
<Major: System/Feature is usable but degraded>

Steps to Reproduce
------------------
- fm event-list --uuid
- Get any event with state "clear"
- fm event-show <uuid>
- Check the "proposed_repair_action" attribute
- cat /var/log/fm-event.log | grep proposed_repair_action
- "proposed_repair_action" attribute is not visible in fm-event.log file

Expected Behavior
------------------
"proposed_repair_action" attribute is present in fm-event.log file

Actual Behavior
----------------
"proposed_repair_action" attribute is not visible in fm-event.log file

Reproducibility
---------------
100% reproducible

System Configuration
--------------------
indifferent

Branch/Pull Time/Commit
-----------------------

Last Pass
---------

Timestamp/Logs
--------------

Test Activity
-------------

Workaround
----------
not worwaround

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/fault/+/899973

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/starlingx/fault/+/899973
Committed: https://opendev.org/starlingx/fault/commit/f8716aa3442308c1bd81361ad11621ffc784096a
Submitter: "Zuul (22348)"
Branch: master

commit f8716aa3442308c1bd81361ad11621ffc784096a
Author: fperez <email address hidden>
Date: Thu Nov 2 12:57:32 2023 -0300

    Add "proposed_repair_action" attr to event log file

    Even when event logs have this attribute available, it is not being
    logged in the /var/log/fm-event.log file. This could result in a lack
    of certain information for external tools that use it.

    Test Plan:
    PASS: Build fm-common package and install it. Then, trigger an alarm
          with 'proposed_repair_action'. Verify its presence in the
          /var/log/fm-event.log
    PASS: Raise an alarm without 'proposed_repair_action'. Check that
          the empty attribute is present.
    PASS: Raise an alarm with a long 'proposed_repair_action'. verify that
          this message is not affecting other attributes.

    Closes-Bug: 2042579

    Change-Id: Ic27b840041872c3afd0be28e11556acf42a3d5a9
    Signed-off-by: fperez <email address hidden>