From 0f09b07166663b1e08a18a4a9b876f1d04aa99c3 Mon Sep 17 00:00:00 2001 From: Todd Malsbary Date: Fri, 21 Jan 2022 13:16:21 -0800 Subject: [PATCH] Delay SriovNetwork deployment after other charts Draining the node (as done by the SR-IOV operator) causes the helm-controller Pod to exit, sometimes leaving Helm releases stuck in a 'pending-install' state. This has been observed during the initial bootstrapping of the pod11 cluster. Signed-off-by: Todd Malsbary Change-Id: Id4c164bfa9b5594ae098e07f71274f6cffccd5b3 --- deploy/site/cluster-icn/sriov-network-release.yaml | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/deploy/site/cluster-icn/sriov-network-release.yaml b/deploy/site/cluster-icn/sriov-network-release.yaml index 30d82a1..f9776da 100644 --- a/deploy/site/cluster-icn/sriov-network-release.yaml +++ b/deploy/site/cluster-icn/sriov-network-release.yaml @@ -19,5 +19,25 @@ spec: upgrade: remediation: retries: -1 + # Deployment of sriov-network causes the SR-IOV operator to drain + # the node, including the Flux controllers. If the Helm controller + # is restarted while a chart install is pending, it is possible that + # the chart state becomes stuck in "pending-install" and manual + # intervention (deleting the Helm secret for the chart) is required + # to fix it. Depending on the other charts in this cluster should + # prevent this issue from occurring. dependsOn: + - name: cdi + - name: cpu-manager + - name: kubevirt + - name: ovn4nfv-network + - name: ovn4nfv + - name: node-feature-discovery + - name: qat-device-plugin - name: sriov-network-operator + - namespace: emco + name: services + - namespace: emco + name: tools + - namespace: emco + name: monitor -- 2.16.6