Move cleartext destructive labels to ginkgo label filters

[Davo911]

What this PR does / why we need it:
Now as Ginkgo label filters are enabled the cleartext bracket labels marking destructive tests should move too.

Release note:

NONE

[kubevirt-bot]

Hi @Davo911. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

[akalenyu]

/test all

[Davo911]

Forgot to commit the changes in the test scripts to pick up the labels
@akalenyu

[Davo911]

Could we kick off the /test all again here @akalenyu

[akalenyu]

sure!
/test all

[akalenyu]

Sorry I missed checking this out.
So I think we have outsiders relying on skipping the destructive test set using ginkgo.skip. Maybe we could go with duplicates for a while until those are fixed?

[Davo911]

You are right, for compatibility, we should keep them both.
As they don't work together at the same time a check is neccesary though.

[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

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign akalenyu for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[coveralls]

coverage: 59.133% (+0.02%) from 59.115%
when pulling d3cc203 on Davo911:move-destructive-flag-to-label-filter
into 54bac42 on kubevirt:main.

[Davo911]

/test all

[Davo911]

/remove-lifecycle stale

[Davo911]

/test pull-containerized-data-importer-e2e-ceph-wffc

[Davo911]

/test pull-containerized-data-importer-e2e-ceph-wffc

[Davo911]

/test pull-containerized-data-importer-e2e-ceph-wffc

[kubevirt-bot]

@Davo911: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-containerized-data-importer-e2e-ceph-wffc	d3cc203	link	true	/test pull-containerized-data-importer-e2e-ceph-wffc

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.