[OchiengEd]

Description of the change:

Given it is possible for a custom resource to be in error / failed state while a new reconcile process is ongoing, it is unnecessary to mark the status of previous Failure conditions to False while the reconcile loop is still running.

The failure condition will be removed when the custom resource is successfully deployed as it works today.

Motivation for the change:

The failure conditions have timestamps and are accurate as at the time of reporting. Therefore, it would be unnecessary and misleading to set the failure condition status to False before the custom resource is successfully deployed.

Checklist

If the pull request includes user-facing changes, extra documentation is required:

• Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
• Add or update relevant sections of the docs website in website/content/en/docs

Closes operator-framework/ansible-operator-plugins#18

[everettraven]

@OchiengEd How do you feel about moving this PR to the new repository for the ansible operator logic?: https://github.com/operator-framework/ansible-operator-plugins

My thinking here is that since we are actively working to remove the ansible logic from this repository and import the new plugin library (I'm working on this in #6583) it would prevent duplication of work to transplant this to the new repo.

[openshift-merge-robot]

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[OchiengEd]

@everettraven Sure, we can move the PR. Don't have an opinion per se where the merge is done.

I can create a new PR in the new repo. Leaving this here until I do so

[OchiengEd]

Issue has been moved to the ansible-operator-plugins repo. See operator-framework/ansible-operator-plugins#14