100.119 PTP alarm prevents reconfiguring mgmt network on subcloud

[Yuxing]

Brief Description
When reconfiguring the mgmt network with "subcloud deploy update command", if the subcloud has alarm
"100.119 controller-0 Precision Time Protocol (PTP) clocking is out of tolerance by more than 1 second", the playbook is not able to lock the subcloud and the reconfig does not happen.

Severity
Minor

Steps to Reproduce
Create a strategy against a subcloud has alarm 100.119

Expected Behavior
Strategy creation succeeded

Actual Behavior
Strategy creation failed

Reproducibility

Reproducible
100% reproducible

System Configuration
DC

Load info (eg: 2022-03-10_20-00-07)
2024-01-31

Last Pass
First time testing

Timestamp/Logs
NA

See timestamp at:
2024-01-31T15:03:16

Alarms
100.199 alarm

Test Activity
Feature testing

Workaround
Wait for 100.119 cleared

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/starlingx/nfv/+/907443
Committed: https://opendev.org/starlingx/nfv/commit/d730d8edc291a7a2f247f873359c832ad3909d36
Submitter: "Zuul (22348)"
Branch: master

commit d730d8edc291a7a2f247f873359c832ad3909d36
Author: Yuxing Jiang <email address hidden>
Date: Thu Feb 1 10:37:44 2024 -0500

    Ignore PTP alarm in vim strategies

    This commit ignores the PTP alarm for SyncE in all the vim strategies
    as it should not impact related operations.

    Test-plan:
    1. Manually raise 100.119 alarm by fmClientCli
    2. Verify kube-rootca-update and system-config-update strategies can
    be created/applied/deleted successfully along with the 100.119 alarm.

    Closes-bug: 2051950
    Change-Id: Ie2cc570c28de95802ff1b88e30f3c9f562b3c892
    Signed-off-by: Yuxing Jiang <email address hidden>