Comment 2 for bug 1981821

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ptp-notification-armada-app (master)

Reviewed: https://review.opendev.org/c/starlingx/ptp-notification-armada-app/+/850057
Committed: https://opendev.org/starlingx/ptp-notification-armada-app/commit/f7475d56083b1fb77b5024668a403967e82e6df0
Submitter: "Zuul (22348)"
Branch: master

commit f7475d56083b1fb77b5024668a403967e82e6df0
Author: Douglas Henrique Koerich <email address hidden>
Date: Fri Jul 15 14:32:09 2022 -0300

    Fix bad ptp4l socket spec for ptptracking

    This change fixes two issues found in the helm chart specification for
    ptp-notification application:
    1) Correct name of socket in the host when legacy PTP configuration is
       found;
    2) Avoid failure in the pod creation when no legacy PTP configuration is
       found, since the original hostPath type "Socket" is required to
       exist, which is not the case in that (valid) scenario. In this case,
       the "type" field is reset which causes the path check to be dismissed

    Test Plan:
    PASS: Pod (containers) running with changed (fixed) ptp-notification tgz

    Closes-Bug: 1981821
    Signed-off-by: Douglas Henrique Koerich <email address hidden>
    Change-Id: I0efc1bdec525366ef09a87f1d0fc311cc5216656