Skip to content
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

Bug 1795412: Print whether CRDs are updated #258

Merged
merged 1 commit into from Feb 5, 2020

Conversation

sttts
Copy link
Contributor

@sttts sttts commented Oct 22, 2019

This will help to see hotloops due to missing defaults in manifests, leading invisibly to https://bugzilla.redhat.com/show_bug.cgi?id=1795412.

@openshift-ci-robot openshift-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Oct 22, 2019
@sttts
Copy link
Contributor Author

sttts commented Oct 22, 2019

/assign @abhinavdahiya @smarterclayton

@abhinavdahiya
Copy link
Contributor

Since clients of the Apply are using updated only to print it, I would prefer that updated remain internal to Apply.. so maybe printing in apply itself.

@openshift-ci-robot openshift-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 5, 2020
@sttts sttts changed the title Print whether resources are updated Print whether CRDs are updated Feb 5, 2020
@sttts sttts changed the title Print whether CRDs are updated Bug 1795412: Print whether CRDs are updated Feb 5, 2020
@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Feb 5, 2020
@openshift-ci-robot
Copy link
Contributor

@sttts: This pull request references Bugzilla bug 1795412, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Bug 1795412: Print whether CRDs are updated

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.

@sttts
Copy link
Contributor Author

sttts commented Feb 5, 2020

@abhinavdahiya added the logging to the apply func, simple twoliner. PTAL. This will help us to diagnose https://bugzilla.redhat.com/show_bug.cgi?id=1795412. Continuous CRD updates increase CPU usage of the apiservers.

@abhinavdahiya
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 5, 2020
@sdodson sdodson added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 5, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, sttts

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit ee4cd7e into openshift:master Feb 5, 2020
@openshift-ci-robot
Copy link
Contributor

@sttts: All pull requests linked via external trackers have merged. Bugzilla bug 1795412 has been moved to the MODIFIED state.

In response to this:

Bug 1795412: Print whether CRDs are updated

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants