New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCPBUGS-16762: Revert "OCPBUGS-16762: Bump openshift/api for container.maxLength fix" #982
Conversation
@Miciah: An error was encountered updating to the POST state for bug OCPBUGS-16762 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details. Full error message.
Error marking step #30230761 finished: root cause: Tried to update an entity that does not exist.: request failed. Please analyze the request body for more details. Status code: 400:
Please contact an administrator to resolve this issue, then request a bug refresh with In response to this:
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/test-infra repository. |
/assign @rfredette |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rfredette 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:
Approvers can indicate their approval by writing |
/hold Revision ed1f91a was retested 3 times: holding |
Rebased for #985. |
ed1f91a
to
49eb058
Compare
/retest |
/jira refresh |
@Miciah: This pull request references Jira Issue OCPBUGS-16762, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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/test-infra repository. |
/jira refresh |
@Miciah: This pull request references Jira Issue OCPBUGS-16762, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
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/test-infra repository. |
I looked at two things:
/lgtm Leaving approval for @rfredette. |
@Miciah: Jira Issue OCPBUGS-16762: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-16762 has been moved to the MODIFIED state. In response to this:
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/test-infra repository. |
@Miciah: 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/test-infra repository. I understand the commands that are listed here. |
Fix included in accepted release 4.15.0-0.nightly-2023-11-07-162411 |
[ART PR BUILD NOTIFIER] This PR has been included in build ose-cluster-ingress-operator-container-v4.15.0-202311202349.p0.g9e77590.assembly.stream for distgit ose-cluster-ingress-operator. |
Reverts #979
The 4.15.0 fix didn't get verified in time to backport it to 4.14.0, so I am reverting the changes in 4.15.0 and will close the 4.14.0 bug report as "Can't Fix".