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

Clean up event messages for errors. #89794

Merged
merged 1 commit into from
Apr 3, 2020

Conversation

msau42
Copy link
Member

@msau42 msau42 commented Apr 2, 2020

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
Error output from some volume clients can be quite verbose. These messages currently propagate to Kubernetes events, which causes a bit of event spam. This change leaves the details to logs instead, and keeps the event message short.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Reduce event spam during a volume operation error.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Apr 2, 2020
@k8s-ci-robot k8s-ci-robot requested review from gnufied and jingxu97 April 2, 2020 21:14
@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. sig/storage Categorizes an issue or PR as relevant to SIG Storage. labels Apr 2, 2020
@msau42
Copy link
Member Author

msau42 commented Apr 2, 2020

/priority important-soon
/sig storage

@k8s-ci-robot k8s-ci-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Apr 2, 2020
@justaugustus
Copy link
Member

cc: @kubernetes/release-managers

@msau42
Copy link
Member Author

msau42 commented Apr 2, 2020

/retest

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed release-note-none Denotes a PR that doesn't merit a release note. labels Apr 2, 2020
Copy link
Member

@saad-ali saad-ali left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 2, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: msau42, saad-ali

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

Change-Id: Ib70b50e676b917c4d976f32ee7a19f8fc63b6bc6
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 2, 2020
@saad-ali
Copy link
Member

saad-ali commented Apr 2, 2020

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 2, 2020
@k8s-ci-robot k8s-ci-robot merged commit 01df16a into kubernetes:master Apr 3, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.19 milestone Apr 3, 2020
k8s-ci-robot added a commit that referenced this pull request Apr 4, 2020
…-upstream-release-1.18

Automated cherry pick of #89794: Clean up event messages for errors.
k8s-ci-robot added a commit that referenced this pull request Apr 9, 2020
…-upstream-release-1.17

Automated cherry pick of #89794: Clean up event messages for errors.
k8s-ci-robot added a commit that referenced this pull request Apr 9, 2020
…-upstream-release-1.16

Automated cherry pick of #89794: Clean up event messages for errors.
k8s-ci-robot added a commit that referenced this pull request Apr 9, 2020
…-upstream-release-1.15

Automated cherry pick of #89794: Clean up event messages for errors.
@msau42 msau42 deleted the cleanup-logs branch July 22, 2021 21:18
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/storage Categorizes an issue or PR as relevant to SIG Storage. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants