[release-4.19] OCPBUGS-60967: Fix job success logic

[openshift-cherrypick-robot]

This is an automated cherry-pick of #3202

/assign sebsoto

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-60771 has been cloned as Jira Issue OCPBUGS-60967. Will retitle bug to link to clone.
/retitle [release-4.19] OCPBUGS-60967: Fix job success logic

In response to this:

This is an automated cherry-pick of #3202

/assign sebsoto

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-60967, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-60771 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

In response to this:

This is an automated cherry-pick of #3202

/assign sebsoto

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.

[sebsoto]

/approve

[sebsoto]

/lgtm

[sebsoto]

/jira refresh

[openshift-ci-robot]

@sebsoto: This pull request references Jira Issue OCPBUGS-60967, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

[sebsoto]

/jira refresh

[openshift-ci-robot]

@sebsoto: This pull request references Jira Issue OCPBUGS-60967, 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.z) matches configured target version for branch (4.19.z)
• 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-60771 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-60771 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0
• bug has dependents

Requesting review from QA contact:
/cc @rrasouli

In response to this:

/jira refresh

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, sebsoto

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

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

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 8247257 and 2 for PR HEAD f8d30c2 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD f94a3e8 and 1 for PR HEAD f8d30c2 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD af047c3 and 0 for PR HEAD f8d30c2 in total

[openshift-ci-robot]

/hold

Revision f8d30c2 was retested 3 times: holding

[sebsoto]

/override ci/prow/aws-e2e-operator ci/prow/azure-e2e-upgrade

[sebsoto]

/hold cancel

[openshift-ci]

@sebsoto: Overrode contexts on behalf of sebsoto: ci/prow/aws-e2e-operator, ci/prow/azure-e2e-upgrade

In response to this:

/override ci/prow/aws-e2e-operator ci/prow/azure-e2e-upgrade

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]

@openshift-cherrypick-robot: 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/aws-e2e-operator	f8d30c2	link	unknown	/test aws-e2e-operator
ci/prow/azure-e2e-upgrade	f8d30c2	link	unknown	/test azure-e2e-upgrade

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.

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-60967: All pull requests linked via external trackers have merged:

• openshift/windows-machine-config-operator#3234

Jira Issue OCPBUGS-60967 has been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #3202

/assign sebsoto

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.

[sebsoto]

/cherry-pick release-4.18

[openshift-cherrypick-robot]

@sebsoto: new pull request created: #3377

In response to this:

/cherry-pick release-4.18

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.