-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Fix missing disruption uploads. #27636
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
Fix missing disruption uploads. #27636
Conversation
Discovered that we are getting no data for image registry since Dec 7th due to PR openshift#27574 which shut off the entire monitor if we have less than the required 100 runs to appear in the file of allowances to enforce. I guess at this time, we did not have enough runs with image registry for 4.13. (which is unusual) Skip the test, but let the monitor run.
|
@dgoodwin: The following tests failed, say
Full PR test history. Your PR dashboard. 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. |
|
/test ci/prow/e2e-aws-ovn-upgrade |
|
@dgoodwin: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
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. |
|
@derekhiggins can you confirm this looks ok? I believe this still avoids the nil pointer you were getting, but now allows the monitoring to run, report to datafile, and eventually end up in bigquery. We started losing data with the original change. |
|
/test e2e-aws-ovn-upgrade |
|
/lgtm
yup, iirc we should be ok as long as its done before the call to "ExpectNoDisruptionForDuration" |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: derekhiggins, dgoodwin 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 |
Discovered that we are getting no data for image registry since Dec 7th
due to PR #27574 which shut off the entire monitor if we have less than
the required 100 runs to appear in the file of allowances to enforce. I
guess at this time, we did not have enough runs with image registry for
4.13. (which is unusual)
Skip the test, but let the monitor run.
TRT-760