Helm release not getting rolled back

[rajpopat27]

I deployed the application v0.3 and it got deployed successfully as is shown below

`NAME    READY   MESSAGE                                 REVISION        SUSPENDED 
prod    True    Release reconciliation succeeded        0.3.0           False    
staging True    Release reconciliation succeeded        0.3.0           False

Now to check the rollback capabilities of flux I changed the helm chart and introduced an error intentionally
I changed the apiVersion of Kubernetes deployment to v1 from apps/v1
And upgraded the chart version to 0.4.0
Now the status of release is as below

NAME    READY   MESSAGE                                                                                                                      REVISION        SUSPENDED 
prod    False   Helm upgrade failed: unable to recognize "": no matches for kind "Deployment" in version "v1"   0.3.0           False    
staging False   Helm upgrade failed: unable to recognize "": no matches for kind "Deployment" in version "v1"   0.3.0           False    

My question is shouldn't helm rollback the release to the previous working version and the status should be ready with v 0.3.0
As the spec.upgrade.remediation.strategy is rollback
This is the helm release CRD

spec:
  chart:
    spec:
      chart: ./
      version: '>=0.0.0 <2.0.0'
      sourceRef:
        kind: GitRepository
        name: demo-app
      valuesFile: values-prod.yaml
  interval: 30s
  releaseName: demo-app-prod
  targetNamespace: prod
  install:
    remediation:
      retries: 3
  upgrade:
    remediation:
      strategy: rollback
      remediateLastFailure: false

[hiddeco]

There is a difference with Helm between a validation error and a release error. When a validation error occurs, no actual release has been made so there is nothing to roll back, and this is likely what you are observing.

You can validate this by inspecting your Helm storage using helm, confirming there hasn't been a new release produced since the last successful release of the controller.

[rajpopat27]

@hiddeco Thanks for the clarification
My organization is thinking of adopting flux for CD but I need to demo the rollback capabilities of flux so how can I go about doing that?
How can I introduce a release error in a Helm Chart??
I am using the following helm chart
https://github.com/rajpopat27/demo-app

[stefanprodan]

We use this in our e2e tests: https://github.com/stefanprodan/podinfo/blob/master/charts/podinfo/values.yaml#L16-L19

[hiddeco]

Bear in mind that if you want to trigger a rollback based (on waiting) on failing probes, the number of replicas needs to be >=2 due to helm/helm#8660