More zuul jobs, and generate JUnitXML reports for KUTTL

[tosky]

Add KUTTL and tempest zuul jobs (meant to replace the prow ones in the long term)

KUTTL: generate JUnitXML reports

• switch the type to XML (the accepted value is 'xml' lowercase, not uppercase);
• tune the name a bit to highlight it is a report;
• add the new reportGranularity parameter which is supported by kuttl 0.20.0 and will restore the pre-1.17 JUnitXML format (granularity by test case, instead of by step);
• remove the URL of kuttl, so that it is not tied to a specific release.

Depends-On: openstack-k8s-operators/ci-framework#2628

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[tosky]

recheck

[tosky]

recheck

[cschwede]

/test all

[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/36199b234d564601ada878d358ea524b

❌ openstack-k8s-operators-content-provider FAILURE in 14m 02s
⚠️ swift-operator-kuttl SKIPPED Skipped due to failed job openstack-k8s-operators-content-provider (non-voting)
⚠️ swift-operator-tempest SKIPPED Skipped due to failed job openstack-k8s-operators-content-provider (non-voting)

[tosky]

I would appreciate some help to understand why the swift-operator kuttl jobs require a few additional variables and why those are not passed around in the code I'm using to trigger the those test

[tosky]

I don't know what happened, but it looks like both tempest and kuttl zuul tests work now!

[tosky]

recheck

[tosky]

recheck

[fmount]

/lgtm

[fmount]

@cschwede to approve ^

[cschwede]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cschwede, 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 [cschwede]

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

[openshift-ci]

@tosky: 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
ci/prow/swift-operator-build-deploy-kuttl	7676a13	link	unknown	/test swift-operator-build-deploy-kuttl

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.