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.

Sign up for GitHub

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

Jump to bottom

[release-4.12] OCPBUGS-18529: Reduce operator and config-daemon verbosity #819

Merged
merged 5 commits into from
Nov 8, 2023
Merged

[release-4.12] OCPBUGS-18529: Reduce operator and config-daemon verbosity #819

merged 5 commits into from
Nov 8, 2023

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #817

/assign zeeke

@zeeke
Set zap log TimeEncoder
b35cbe0 
Set a TimeEncoder for zap logging system
to have more speaking timestamp.

from `1.6893201844680622e+09` to
`2023-07-14T09:52:29.539392293Z`

Signed-off-by: Andrea Panattoni <[email protected]>
@zeeke
Reduce SriovOperator verbosity
792575e 
In `renderDevicePluginConfigData()`, avoid
logging the full ResourceList for every resource in the loop.

Avoid logging in helper functions, as they can be invoked in loops.

Signed-off-by: Andrea Panattoni <[email protected]>
@zeeke
Avoid logging devlink warning
25b1d3a 
Devlink mode is not supported by every SR-IOV NIC model.

Signed-off-by: Andrea Panattoni <[email protected]>
@zeeke
Reduce vebosity of config-damon
e398bdb 
Log `getLinkType(): ...` only if LogLevel == 2

Signed-off-by: Andrea Panattoni <[email protected]>
@zeeke
Avoid reconciling policies multiple times
3692e2b 
`SriovNetworkNodePolicy` reconcile function lists all node policies
and updates all SriovNetworkNodeState. Hence there is no need to
resync all of them periodically.

Avoid triggering multiple reconciliations when creating multiple
policies in a row (that is what happens when using yaml files).

Signed-off-by: Andrea Panattoni <[email protected]>
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Sep 5, 2023
Merged
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-18451 has been cloned as Jira Issue OCPBUGS-18529. Will retitle bug to link to clone.
/retitle [release-4.12] OCPBUGS-18529: Reduce operator and config-daemon verbosity

In response to this:

This is an automated cherry-pick of #817

/assign zeeke

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.

@openshift-ci openshift-ci bot changed the title [release-4.12] OCPBUGS-18451: Reduce operator and config-daemon verbosity [release-4.12] OCPBUGS-18529: Reduce operator and config-daemon verbosity Sep 5, 2023
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 5, 2023
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-18529, which is invalid:

  • expected dependent Jira Issue OCPBUGS-18451 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #817

/assign zeeke

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.

@openshift-ci openshift-ci bot requested review from bn222 and pliurh September 5, 2023 08:22
@zeeke
Copy link
Contributor

zeeke commented Sep 8, 2023

/jira refresh

@SchSeba , @bn222 please take a look

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 8, 2023
@openshift-ci-robot
Copy link
Contributor

@zeeke: This pull request references Jira Issue OCPBUGS-18529, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.12.z) matches configured target version for branch (4.12.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-18451 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-18451 targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.z
  • bug has dependents

Requesting review from QA contact:
/cc @zhaozhanqi

In response to this:

/jira refresh

@SchSeba , @bn222 please take a look

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.

@bn222
Copy link
Contributor

bn222 commented Sep 18, 2023

/lgtm
/backport-risk-assessed
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 18, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 18, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bn222, openshift-cherrypick-robot

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-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 18, 2023
@bn222
Copy link
Contributor

bn222 commented Sep 18, 2023

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Sep 18, 2023
@zeeke
Copy link
Contributor

zeeke commented Oct 4, 2023

@zhaozhanqi please take a look at this

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 18, 2023

@openshift-cherrypick-robot: 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.

@zeeke
Copy link
Contributor

zeeke commented Oct 20, 2023

@zhaozhanqi please,take a look when you have time

@zhaozhanqi
Copy link

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Nov 8, 2023
@zhaozhanqi
Copy link

@zhaozhanqi please,take a look when you have time

sorry, I missed this one

@openshift-merge-bot openshift-merge-bot bot merged commit bda7c22 into openshift:release-4.12 Nov 8, 2023
3 checks passed
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-18529: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-18529 has been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #817

/assign zeeke

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
Reviewers

@bn222 bn222 Awaiting requested review from bn222

@pliurh pliurh Awaiting requested review from pliurh

@zhaozhanqi zhaozhanqi Awaiting requested review from zhaozhanqi

Assignees

@mffiedler mffiedler

@rbbratta rbbratta

@zeeke zeeke

@weliang1 weliang1

@bn222 bn222

@anuragthehatter anuragthehatter

@huiran0826 huiran0826

@asood-rh asood-rh

@jechen0648 jechen0648

@qiowang721 qiowang721

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.