-
Notifications
You must be signed in to change notification settings - Fork 150
Bug 1781475: Avoid console_url metric as empty string [Release-4.2] #360
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
Conversation
|
@benjaminapetersen: An error was encountered adding this pull request to the external tracker bugs for bug 1781475 on the Bugzilla server at https://bugzilla.redhat.com:
Please contact an administrator to resolve this issue, then request a bug refresh with DetailsIn 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. |
|
/bugzilla refresh Strange. Will try it again once before attempting to resolve otherwise. |
|
@benjaminapetersen: An error was encountered adding this pull request to the external tracker bugs for bug 1781475 on the Bugzilla server at https://bugzilla.redhat.com:
Please contact an administrator to resolve this issue, then request a bug refresh with DetailsIn 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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: benjaminapetersen The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/bugzilla refresh Checking to see if special characters in my title goofed it up. |
|
@benjaminapetersen: An error was encountered adding this pull request to the external tracker bugs for bug 1781475 on the Bugzilla server at https://bugzilla.redhat.com:
Please contact an administrator to resolve this issue, then request a bug refresh with DetailsIn 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. |
|
Nope. |
|
For the record, this is a bug in bugzilla that is being pursued. |
|
I've confirmed the target release is correct and the corresponding 4.3 bug is verified. Manually adding the valid bug label since the bot is broken. |
|
/bugzilla refresh |
|
@petr-muller: This pull request references Bugzilla bug 1781475, which is valid. The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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. |
|
/retest Lets see now if things are working again. |
|
flake |
|
@benjaminapetersen: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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. |
|
panic error from the console-operator pod |
|
Exciting, I need to swing back on this one. |
|
Closing, 4.2 is too far back for such a low sev bug. |
|
@benjaminapetersen: This pull request references Bugzilla bug 1781475. The bug has been updated to no longer refer to the pull request using the external bug tracker. DetailsIn 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. |
Manual backport of #346
legacy-registrydue to the global registry issues with Prometheus. I believe this issue appeared inkubernetes-1.15, which is 4.3+. The files included have been adjusted to use the original global registry.