Open
Description
Bug Report
There is a hot loop in the CSV state machine. If the bundle contains a malformed/invalid resource, e.g. if the deployment name is invalid, the CSV will go from Pending -> InstallReady -> Failed -> Pending ...
This was the cause of the flakyness seem in failforward e2e.
PR #3572 disables this test until we can fix this.