Delete allocated PVCs after each kuttl test execution

[fmount]

Currently Zuul kuttl jobs fail due to the fact we're not de-allocating PVCs after each kuttl test execution. This patch aims to improve the cleanup process by removing them as part of the cleanup step.

Jira: https://issues.redhat.com/browse/OSPRH-22400

[softwarefactory-project-zuul]

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/bdb65f0897d64acda571b06bed584fab

❌ openstack-k8s-operators-content-provider TIMED_OUT in 30m 56s
⚠️ glance-operator-kuttl SKIPPED Skipped due to failed job openstack-k8s-operators-content-provider (non-voting)
⚠️ glance-operator-tempest SKIPPED Skipped due to failed job openstack-k8s-operators-content-provider (non-voting)

[fmount]

recheck

[fmount]

/test glance-operator-build-kuttl

[fmount]

recheck

[fmount]

/test glance-operator-build-kuttl

[fmount]

recheck

[fmount]

/test glance-operator-build-kuttl

[fmount]

recheck

[fmount]

/test glance-operator-build-kuttl

[fmount]

recheck

[fmount]

recheck

[tosky]

For the record, as discussed with @fmount, it is not feasible to add a shared code to delete the resources because the tests are not really independent (same test suite)

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fmount, tosky

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 [fmount]

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

[tosky]

/cherry-pick 18.0-fr4

[openshift-cherrypick-robot]

@tosky: #838 failed to apply on top of branch "18.0-fr4":

Applying: Delete allocated PVCs after each kuttl test execution
Applying: Do not deploy additional ceph services
Using index info to reconstruct a base tree...
M	zuul.d/jobs.yaml
Falling back to patching base and 3-way merge...
Auto-merging zuul.d/jobs.yaml
CONFLICT (content): Merge conflict in zuul.d/jobs.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0002 Do not deploy additional ceph services

In response to this:

/cherry-pick 18.0-fr4

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.

[fmount]

I think it's ok to not cherry pick this change and target the CI bump to FR5 along with Ceph Tentacle

[tosky]

I think it's ok to not cherry pick this change and target the CI bump to FR5 along with Ceph Tentacle

I thought it made sense to at least have the jobs working in 18.0-fr4, otherwise they just burn CPU time without being useful at all.
I wouldn't make them voting on 18.0-fr4, but it may be useful to have them around. I guess we need to backport something else too.