starlingx/ptp-notification-armada-app
Code Issues Proposed changes

Fix bad ptp4l socket spec for ptptracking

Browse Source 
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 <douglashenrique.koerich@windriver.com>
Change-Id: I0efc1bdec525366ef09a87f1d0fc311cc5216656
This commit is contained in:
Douglas Henrique Koerich 2022-07-15 14:32:09 -03:00
parent e72365d710
commit f7475d5608
2 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
stx-ptp-notification-helm/stx-ptp-notification-helm/helm-charts/ptp-notification/templates/daemonset.yaml
View File

@ -166,7 +166,6 @@ spec:
- name: varrun
hostPath:
path: {{ .Values.ptptracking.ptp4lSocket }}
type: Socket
{{ end }}
- name: pmc
hostPath:

2
stx-ptp-notification-helm/stx-ptp-notification-helm/helm-charts/ptp-notification/values.yaml
View File

@ -66,7 +66,7 @@ location:
ptptracking:
imagePullSecrets: default-registry-key
ptp4lSocket: /var/run/ptp4l-legacy
ptp4lSocket: /var/run/ptp4l-ptp4l-legacy
ptp4lServiceName: ptp4l-legacy
phc2sysServiceName: phc2sys-legacy
image: