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
[release-4.6] Bug 1893681: Bulk port creation exception not completely formatted #390
[release-4.6] Bug 1893681: Bulk port creation exception not completely formatted #390
Conversation
In our client, for OpenStack client, we created a workaround for missing bulk port create (at that time). Turns out, that running out of the OpenStack resources, there could be SDKException thrown, which is fine, although due to the mistake, message wasn't informative at all. This patch is fixing this. Closes-Bug: 1901666 Change-Id: Iba0744840231088018ec37cb6e3d98e1df6916fa (cherry picked from commit 2b3e2f5)
@openshift-cherrypick-robot: Bugzilla bug 1890472 has been cloned as Bugzilla bug 1893681. Retitling PR to link against new bug. 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. |
@openshift-cherrypick-robot: This pull request references Bugzilla bug 1893681, which is invalid:
Comment 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. |
/approve |
/bugzilla refresh |
@luis5tb: This pull request references Bugzilla bug 1893681, which is valid. 6 validation(s) were run on this bug
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. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: luis5tb, openshift-cherrypick-robot 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 |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale This is still a thing for sure. Unless such bugs are not mergeable into 4.6 anymore I'd still like fix to get in. I don't think severity/low bugs had any chance to get merged into 4.6 yet. |
@openshift-cherrypick-robot: All pull requests linked via external trackers have merged: Bugzilla bug 1893681 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. |
more accuratly alert on a single nodes iptable stale
This is an automated cherry-pick of #389
/assign gryf