Closed rhmdnd closed 2 months ago
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rhmdnd
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@rhmdnd: The following tests failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
ci/prow/e2e-aws | a991252ebe6c0ee5af976b13d8a3d59b428ad6ab | link | true | /test e2e-aws |
ci/prow/e2e-bundle-aws | a991252ebe6c0ee5af976b13d8a3d59b428ad6ab | link | true | /test e2e-bundle-aws |
ci/prow/e2e-bundle-aws-upgrade | a991252ebe6c0ee5af976b13d8a3d59b428ad6ab | link | true | /test e2e-bundle-aws-upgrade |
Full PR test history. Your PR dashboard.
Debugging the e2e failures in https://github.com/openshift/file-integrity-operator/pull/541
This was already incorporated into https://github.com/openshift/file-integrity-operator/pull/539
By default, the File Integrity Operator would set node selectors and taints that would only allow it to schedule on
master
nodes. While this is fine for OpenShift environments, some additional environments we test on, like Red Hat OpenShift on AWS (ROSA), don't providemaster
nodes at all.To accomodate this in our testing and tooling, this commit removes the node selector and taint from the default bundle, and moves it into an OpenShift-specific bundle where it will still get used for OpenShift deploy paths and bundles.
This will be more useful in a future patch that implements support for running File Integrity Operator end-to-end testing on ROSA HCP, which only provides
worker
nodes and notmaster
nodes.