fperez f8716aa344 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 <fabrizio.perez@windriver.com>
2023-11-02 19:07:49 +00:00
2019-04-19 19:52:34 +00:00
2023-04-28 12:38:51 -04:00
2021-09-01 08:58:34 -04:00
2018-05-31 07:36:00 -07:00
2023-05-31 16:36:27 +00:00
2023-07-19 10:48:29 -03:00
2023-03-02 19:32:25 +00:00

Fault Management (FM)

The starlingx/fault repository handles Fault Management (FM) services1, and provides the fm command-line interface (CLI)2.

This repository is not intended to be developed standalone, but rather as part of the StarlingX Source System, which is defined by the StarlingX manifest3.

References


  1. https://docs.starlingx.io/api-ref/fault↩︎

  2. https://docs.starlingx.io/cli_ref/fm.html↩︎

  3. https://opendev.org/starlingx/manifest.git↩︎

Description
StarlingX Fault Management
Readme 5.8 MiB
Languages
Python 60.9%
C++ 31.7%
Shell 3.1%
C 3.1%
Makefile 1.1%