We've observed a couple of scenarios that lead us to believe the test tests.install_upgrade_operators.daemonset.test_daemonset_params.test_no_new_cnv_daemonset_added should be removed in all branches:

• The hostpath-provisioner CR isn't deployed automatically and, in some cases, isn't deployed at all on infrastructures like OCI, AWS, or GCP. In such instances, the hostpath-provisioner-csi daemonset won't be deployed.

• During a recent run in version 4.14, a new DaemonSet in openshift-cnv caused the test to fail. This DaemonSet is ovs-cni-amd64, and upon reviewing the operator, its deployment is configured in the NetworkAddonsConfigSpec CR (ref).

Therefore, to make the test suite resilient to running on various infrastructures and under different conditions, we propose to remove this test. Our reasoning is as follows:

• The test suite already includes functional tests that ensure the necessary OpenShift infrastructure is successfully deployed and operational. It's not truly necessary to check implementation details like the running DaemonSets.

• Given that the combination of configurations and infrastructures is constantly growing, the effort required to keep this test resilient across all these combinations is simply not worthwhile.