[release-4.16] OCPBUGS-36137: fix sorting unpack jobs

[ankitathomas]

Manual cherry-pick of 9c4ea26 to 4.16

[openshift-ci-robot]

@ankitathomas: This pull request references Jira Issue OCPBUGS-34173, which is invalid:

• expected the bug to target either version "4.16." or "openshift-4.16.", but it targets "4.17.0" instead
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
• expected Jira Issue OCPBUGS-34173 to depend on a bug targeting a version in 4.17.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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:

Manual cherry-pick of 9c4ea26 to 4.16

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: ankitathomas

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:

• DOWNSTREAM_OWNERS [ankitathomas]

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]

@ankitathomas: This pull request references Jira Issue OCPBUGS-36137, 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"
• expected Jira Issue OCPBUGS-36137 to depend on a bug targeting a version in 4.17.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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:

Manual cherry-pick of 9c4ea26 to 4.16

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.

[ankitathomas]

/jira refresh

[openshift-ci-robot]

@ankitathomas: This pull request references Jira Issue OCPBUGS-36137, 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"
• expected Jira Issue OCPBUGS-36137 to depend on a bug targeting a version in 4.17.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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.

[ankitathomas]

/jira refresh

[openshift-ci-robot]

@ankitathomas: This pull request references Jira Issue OCPBUGS-36137, 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"

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.

[ankitathomas]

/jira refresh

[openshift-ci-robot]

@ankitathomas: This pull request references Jira Issue OCPBUGS-36137, 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.16.0) matches configured target version for branch (4.16.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-34173 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-34173 targets the "4.17.0" version, which is one of the valid target versions: 4.17.0
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request.

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.

[perdasilva]

/retest

[jianzhangbjz]

Test pass, details: https://issues.redhat.com/browse/OCPBUGS-36137
/lgtm
/cherry-pick-approved

[jianzhangbjz]

/label qe-approved
/label cherry-pick-approved

[openshift-ci-robot]

@ankitathomas: This pull request references Jira Issue OCPBUGS-36137, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.0) matches configured target version for branch (4.16.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-34173 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-34173 targets the "4.17.0" version, which is one of the valid target versions: 4.17.0
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request.

In response to this:

Manual cherry-pick of 9c4ea26 to 4.16

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.

[ankitathomas]

/retest

[ankitathomas]

/retest

[perdasilva]

/retest

[kevinrizza]

/label backport-risk-assessed

[kevinrizza]

/retest

[perdasilva]

/retest

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 555e529 and 2 for PR HEAD 782e7f8 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD abccea9 and 1 for PR HEAD 782e7f8 in total

[openshift-ci]

@ankitathomas: all tests passed!

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]

@ankitathomas: Jira Issue OCPBUGS-36137: All pull requests linked via external trackers have merged:

• openshift/operator-framework-olm#799

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

In response to this:

Manual cherry-pick of 9c4ea26 to 4.16

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-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build operator-lifecycle-manager-container-v4.16.0-202407082208.p0.gf0be27d.assembly.stream.el9 for distgit operator-lifecycle-manager.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build operator-registry-container-v4.16.0-202407082208.p0.gf0be27d.assembly.stream.el9 for distgit operator-registry.
All builds following this will include this PR.

[ankitathomas]

/cherry-pick release-4.15

[openshift-cherrypick-robot]

@ankitathomas: new pull request created: #817

In response to this:

/cherry-pick release-4.15

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.