-
Notifications
You must be signed in to change notification settings - Fork 46
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
Add logs for quota namespace syncing with verbosity level 2 #119
Add logs for quota namespace syncing with verbosity level 2 #119
Conversation
/cc @ingvagabund |
2820bd7
to
27ca1b2
Compare
@ingvagabund as we talked earlier, I have added more logs from your commit ingvagabund@c6a91c6 |
Thx! Let's see how many new log lines the CI will produce. |
27ca1b2
to
0c14ec2
Compare
/approve |
@ardaguclu: 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ardaguclu, ingvagabund, soltysh 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 |
There is a flaky test failure which is tracked in https://issues.redhat.com/browse/OCPBUGS-15568 in regards to
cluster quota. Up to this point, investigations(openshift/origin#28026, openshift/origin#28032) proved that quota reconciliation does not update
ClusterResourceQuotaStatus
with the matching namespaces accordingly(as seen in the example failed job) (actually it does not updateClusterResourceQuotaStatus
at all).This PR adds more logs to better investigate the problem. Since these logs are being added with verbosity level 2, there might not be needed to revert these logs, once investigation is completed, unless it generates noise in CI jobs.