Commit ba81f82
committed
resource/helm_release: don't skip the uninstall when the release lookup fails
resourceReleaseExists reports false both when a release is genuinely absent
and when the lookup against the cluster failed, telling the two apart only
through the returned diagnostics. Delete acts on the boolean before appending
those diagnostics, so a failed lookup is indistinguishable from "already
uninstalled": the function returns early, the resource is removed from state,
and the uninstall never runs. The release stays behind in the cluster with
nothing tracking it.
We ran into the underlying error during a short API server outage on AKS,
where the same hiccup surfaced in the kubernetes provider as
"net/http: TLS handshake timeout".
Check the diagnostics first, which is what Create already does.
The identical ordering issue in Read is being fixed in #1734, so it is left
alone here.1 parent a4f1c1d commit ba81f82
2 files changed
Lines changed: 12 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1251 | 1251 | | |
1252 | 1252 | | |
1253 | 1253 | | |
| 1254 | + | |
| 1255 | + | |
| 1256 | + | |
| 1257 | + | |
| 1258 | + | |
| 1259 | + | |
1254 | 1260 | | |
1255 | | - | |
1256 | | - | |
1257 | | - | |
1258 | 1261 | | |
1259 | 1262 | | |
1260 | 1263 | | |
1261 | 1264 | | |
| 1265 | + | |
| 1266 | + | |
| 1267 | + | |
1262 | 1268 | | |
1263 | 1269 | | |
1264 | 1270 | | |
| |||
0 commit comments