Details missing from FM events.yaml file

[Agustin Carranza]

Brief Description
-----------------
There is no Context set for 900.006. It should be StarlingX
Note that 900.007 is also missing context as are several other records. If they should not be documented, please set Context: none
The alarms for 100.105, 100.112, 100.113, 300.001 and 300.002 are tagged as Context: starlingx but should be Context: openstack

Severity
--------
Minor: System/Feature is usable with minor issue

Steps to Reproduce
------------------
N/A

Expected Behavior
------------------
Context value has correct info for some alarms.

Actual Behavior
----------------
Context value has incorrent info for some alarms.

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

System Configuration
--------------------
All of them.

Branch/Pull Time/Commit
-----------------------
stx8.0, master

Last Pass
---------
N/A

Timestamp/Logs
--------------
N/A

Test Activity
-------------
Normal use

Workaround
----------
N/A

[OpenStack Infra (hudson-openstack)]

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

commit dad8caed918b49267d7d659f13d972e015957f64
Author: Agustin Carranza <email address hidden>
Date: Mon Mar 27 17:42:43 2023 -0300

    Fix Context value for some alarms

    Some documentation generating scripts were introduced in order to avoid
    manual intervention every time an alarm/log is changed/added/removed.
    Those scripts required a way to know where the alarm/log belongs to.
    For that requirement, the field Context was introduced in previous
    commits. During that development, it was taken the current
    classification at that time in the docs as source of truth, but it was
    outdated.

    This commits modifies the values that were detected as wrong/outdated.
    The scripts also require the value 'none' in the Context field for when
    an alarm/log should not be included in the documentation but still be
    defined in the events.yaml file. So the Context value is updated for
    that case too.

    Context incorrectly tagged as openstack and changed to starlingx:
    * 900.006

    Context incorrectly tagged as starlingx and changed to openstack:
    * 100.105
    * 100.112
    * 100.113
    * 300.001
    * 300.002

    Closes-bug: 2012981

    Test plan
    PASS: Since the Context field does not have impact in functionality,
          build and install fm-doc package successfully.
          Check the file in the filesystem contains this change.
    PASS: Trigger random alarms and check FM functionality.

    Signed-off-by: Agustin Carranza <email address hidden>
    Change-Id: I16f858bbb712349f08b2ceca33152e365b0ed733

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: r/stx.8.0
Review: https://review.opendev.org/c/starlingx/fault/+/880057

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/starlingx/fault/+/880057
Committed: https://opendev.org/starlingx/fault/commit/a3b5c0facf63b3be140daf011d331d10563e86dd
Submitter: "Zuul (22348)"
Branch: r/stx.8.0

commit a3b5c0facf63b3be140daf011d331d10563e86dd
Author: Agustin Carranza <email address hidden>
Date: Mon Mar 27 17:42:43 2023 -0300

    Fix Context value for some alarms

    Some documentation generating scripts were introduced in order to avoid
    manual intervention every time an alarm/log is changed/added/removed.
    Those scripts required a way to know where the alarm/log belongs to.
    For that requirement, the field Context was introduced in previous
    commits. During that development, it was taken the current
    classification at that time in the docs as source of truth, but it was
    outdated.

    This commits modifies the values that were detected as wrong/outdated.
    The scripts also require the value 'none' in the Context field for when
    an alarm/log should not be included in the documentation but still be
    defined in the events.yaml file. So the Context value is updated for
    that case too.

    Context incorrectly tagged as openstack and changed to starlingx:
    * 900.006

    Context incorrectly tagged as starlingx and changed to openstack:
    * 100.105
    * 100.112
    * 100.113
    * 300.001
    * 300.002

    Closes-bug: 2012981

    Test plan
    PASS: Since the Context field does not have impact in functionality,
          build and install fm-doc package successfully.
          Check the file in the filesystem contains this change.
    PASS: Trigger random alarms and check FM functionality.

    Signed-off-by: Agustin Carranza <email address hidden>
    Change-Id: I16f858bbb712349f08b2ceca33152e365b0ed733
    (cherry picked from commit dad8caed918b49267d7d659f13d972e015957f64)