Open okozachenko1203 opened 1 year ago
@okozachenko1203 I often run into this too in a bad / failed deployment. I think one solution would be to run the Helm module with force
if we detect the HelmRelease
is in a bad state?
Alternatively, we can go and fix this upstream in the Helm module so that it can automatically handle this, since it'll be much faster to handle inside the module rather than adding multiple tasks.
We can also vendor the module into our code until the Kubernetes collection releases a new version.
Context
I faced a failure with the following error during atmosphere converge(without any tagging, just ran the full playbook)
poetry run molecule converge -s default
.I jumped into ctl1 node and checked the HelmRelease status and it was
failed
.I tried to redeploy neutron
poetry run molecule converge -s default -- -- --tags neutron
. This time the chart deployment task passed without any error but HelmRelease was neither updated or replaced. Therefore finally failed atWait until network service ready
task.Expected result
Neutron HelmRelease should be redeployed.
Workaround
Need to remove failed HelmRelease manually and rerun the playbook.
Solution?
Helm chart deployment task is performed by
kubernetes.core.helm
module. Need to get the status of HelmRelease if exists already and if it is under failed status, do redeploy or sth.