[release-4.19] OCPBUGS-57019, OPRUN-3914: [Default Catalog Consistency Test]: fix junit output format to allow generate xml

[openshift-cherrypick-robot]

This is an automated cherry-pick of #366

/assign camilamacedo86

/cherrypick release-4.18 release-4.17

[openshift-ci-robot]

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: OPRUN-3914
Jira Issue OCPBUGS-56956 has been cloned as Jira Issue OCPBUGS-57019. Will retitle bug to link to clone.
/retitle [release-4.19] OCPBUGS-57019, OPRUN-3914: [Default Catalog Consistency Test]: fix junit output format to allow generate xml

In response to this:

This is an automated cherry-pick of #366

/assign camilamacedo86

/cherrypick release-4.18 release-4.17

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-57019, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.0) matches configured target version for branch (4.19.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-56956 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-56956 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references OPRUN-3914 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "4.19." or "openshift-4.19.", but it targets "4.20" instead.

In response to this:

This is an automated cherry-pick of #366

/assign camilamacedo86

/cherrypick release-4.18 release-4.17

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 openshift-eng/jira-lifecycle-plugin repository.

[camilamacedo86]

/test openshift-e2e-aws

[anik120]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: anik120, openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign joelanford 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:

• DOWNSTREAM_OWNERS

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

[camilamacedo86]

/test openshift-e2e-aws

[camilamacedo86]

/test openshift-e2e-aws

[camilamacedo86]

/test openshift-e2e-aws

[camilamacedo86]

/hold cancel

[camilamacedo86]

/hold

I will add all required changes in this jira OCPBug to facilitate

[openshift-ci]

@openshift-cherrypick-robot: 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/openshift-e2e-aws	04a28cf	link	true	/test openshift-e2e-aws

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.

[camilamacedo86]

Closed it favour of : #374
(to make easier the validations and low effort for the team)

/close

[camilamacedo86]

/close

[openshift-ci]

@camilamacedo86: Closed this PR.

In response to this:

Closed it favour of : #374
(to make easier the validations and low effort for the team)

/close

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.

[openshift-ci]

@camilamacedo86: Closed this PR.

In response to this:

/close

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.