Closed hasueki closed 1 month ago
@hasueki: This pull request references Jira Issue OCPBUGS-37302, which is invalid:
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.
/retest-required
/approve /lgtm
/retest-required
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hasueki, rtheis, sjenning
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/jira refresh
@rtheis: This pull request references Jira Issue OCPBUGS-37302, which is invalid:
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.
@hasueki how do we get the fix on main verified faster so we can proceed with this PR?
/jira refresh
@hasueki: This pull request references Jira Issue OCPBUGS-37302, which is valid. The bug has been moved to the POST state.
No GitHub users were found matching the public email listed for the QA contact in Jira (jiezhao@redhat.com), skipping review request.
@hasueki are we able to bypass the Red Hat Konflux check?
/retest-required
/retest
/override "Red Hat Konflux / hypershift-release-mce-26-on-pull-request"
@bryan-cox: Overrode contexts on behalf of bryan-cox: Red Hat Konflux / hypershift-release-mce-26-on-pull-request
@hasueki: Jira Issue OCPBUGS-37302: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-37302 has been moved to the MODIFIED state.
[ART PR BUILD NOTIFIER]
Distgit: hypershift This PR has been included in build ose-hypershift-container-v4.16.0-202407231906.p0.gbdf469e.assembly.stream.el9. All builds following this will include this PR.
Fix included in accepted release 4.16.0-0.nightly-2024-07-23-215437
What this PR does / why we need it: Supersedes https://github.com/openshift/hypershift/pull/4393
Which issue(s) this PR fixes (optional, use
fixes #<issue_number>(, fixes #<issue_number>, ...)
format, where issue_number might be a GitHub issue, or a Jira story: Fixes #Checklist