Adil Ghaffar
Adil Ghaffar
@sbueringer This also seems like the cause of the flake that we see in clusterctl upgrade tests from `0.4->1.4` or `0.4->1.5`. ref: https://github.com/kubernetes-sigs/cluster-api/issues/9688
I am looking into this one.
Adding a bit more explanation regarding failures. We have three failures in clusterctl upgrade: - `exec.ExitError` This one happens at `Applying the cluster template yaml to the cluster`, I opened...
Update on this issue. I am not seeing following flakes anymore: - `exec.ExitError` - `failed to find releases` `failed to discovery ownerGraph types` flake is still happening but only when...
> @adilGhaffarDev So the clusterctl upgrade test is 100% stable apart from "failed to discovery ownerGraph types flake is still happening but only when upgrading from (v0.4=>current)"? sorry for the...
> @adilGhaffarDev `exec.ExitError` does not occur anymore because I improved the error output here: `exec.ExitError` was happening at step: `INFO: Applying the cluster template yaml to the cluster ` I...
> Just not sure what changed as I don't remember fixing/changing anything there. This is the new error that was happening after your PR, it seems like it stopped happening...
Little more explanation to clusterctl upgrade failure. Now we are seeing only one flake when upgrading from `0.4->1.4` or `0.4->1.5`, as mentioned before. Its failing with following error: `failed to...
> 🤔 : may be helpful to collect cert-manager resources + logs to analyse this. Or is this locally reproducible? I haven't been able to reproduce locally. I have ran...