[release-1.8] dataImportCronTemplates: Remove CentOS 7 & stream 8

[0xFelix]

What this PR does / why we need it:

This is a manual backport of https://github.com/kubevirt/hyperconverged-cluster-operator/pull/3048.

Reviewer Checklist

Reviewers are supposed to review the PR for every aspect below one by one. To check an item means the PR is either "OK" or "Not Applicable" in terms of that item. All items are supposed to be checked before merging a PR.

• [ ] PR Message
• [ ] Commit Messages
• [ ] How to test
• [ ] Unit Tests
• [ ] Functional Tests
• [ ] User Documentation
• [ ] Developer Documentation
• [ ] Upgrade Scenario
• [ ] Uninstallation Scenario
• [ ] Backward Compatibility
• [ ] Troubleshooting Friendly

Jira Ticket:

https://issues.redhat.com/browse/CNV-45852

Release note:

CentOS 7 & CentOS stream 8 are now EOL so the associated `DataImportCronTemplates` have been removed

[coveralls]

Pull Request Test Coverage Report for Build 10560324470

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 85.646%

---

Totals
Change from base Build 8703919399:	0.0%
Covered Lines:	4690
Relevant Lines:	5476

---

💛 - Coveralls

[hco-bot]

hco-e2e-kv-smoke-gcp lane succeeded. /override ci/prow/hco-e2e-kv-smoke-azure

[kubevirt-bot]

@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-kv-smoke-azure

In response to this:

hco-e2e-kv-smoke-gcp lane succeeded. /override ci/prow/hco-e2e-kv-smoke-azure

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-sigs/prow repository.

[sonarqubecloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[tiraboschi]

/approve

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tiraboschi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• ~~OWNERS~~ [tiraboschi]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

[hco-bot]

hco-e2e-upgrade-index-sno-aws lane succeeded. /override ci/prow/hco-e2e-upgrade-index-sno-azure hco-e2e-upgrade-index-aws lane succeeded. /override ci/prow/hco-e2e-upgrade-index-azure

[kubevirt-bot]

@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-upgrade-index-azure, ci/prow/hco-e2e-upgrade-index-sno-azure

In response to this:

hco-e2e-upgrade-index-sno-aws lane succeeded. /override ci/prow/hco-e2e-upgrade-index-sno-azure hco-e2e-upgrade-index-aws lane succeeded. /override ci/prow/hco-e2e-upgrade-index-azure

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-sigs/prow repository.

[0xFelix]

/retest-required

[hco-bot]

hco-e2e-upgrade-prev-index-aws lane succeeded. /override ci/prow/hco-e2e-upgrade-prev-index-azure

[kubevirt-bot]

@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-upgrade-prev-index-azure

In response to this:

hco-e2e-upgrade-prev-index-aws lane succeeded. /override ci/prow/hco-e2e-upgrade-prev-index-azure

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-sigs/prow repository.

[hco-bot]

hco-e2e-upgrade-prev-index-aws lane succeeded. /override ci/prow/hco-e2e-upgrade-prev-index-azure

[kubevirt-bot]

@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-upgrade-prev-index-azure

In response to this:

hco-e2e-upgrade-prev-index-aws lane succeeded. /override ci/prow/hco-e2e-upgrade-prev-index-azure

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-sigs/prow repository.

[0xFelix]

/retest

[0xFelix]

@tiraboschi The CI failures do not seem to be related to my changes. I see GLIBC mismatch errors. Are these lanes still able to pass at all?

[0xFelix]

/retest

[openshift-ci[bot]]

@0xFelix: 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/hco-e2e-upgrade-prev-index-azure	a026fcea07dbe5d2db21239fba4eae56fb245800	link	true	/test hco-e2e-upgrade-prev-index-azure
ci/prow/hco-e2e-image-index-gcp	a026fcea07dbe5d2db21239fba4eae56fb245800	link	true	/test hco-e2e-image-index-gcp
ci/prow/hco-e2e-image-index-sno-azure	a026fcea07dbe5d2db21239fba4eae56fb245800	link	false	/test hco-e2e-image-index-sno-azure
ci/prow/hco-e2e-image-index-sno-aws	a026fcea07dbe5d2db21239fba4eae56fb245800	link	false	/test hco-e2e-image-index-sno-aws
ci/prow/hco-e2e-upgrade-prev-index-sno-aws	a026fcea07dbe5d2db21239fba4eae56fb245800	link	false	/test hco-e2e-upgrade-prev-index-sno-aws
ci/prow/hco-e2e-image-index-aws	a026fcea07dbe5d2db21239fba4eae56fb245800	link	true	/test hco-e2e-image-index-aws
ci/prow/hco-e2e-upgrade-prev-index-sno-azure	a026fcea07dbe5d2db21239fba4eae56fb245800	link	false	/test hco-e2e-upgrade-prev-index-sno-azure
ci/prow/hco-e2e-image-index-azure	a026fcea07dbe5d2db21239fba4eae56fb245800	link	true	/test hco-e2e-image-index-azure

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

[kubevirt-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale