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

NO-JIRA: manifests: bump loglevel of operator to normal #895

Merged

Conversation

lance5890
Copy link
Contributor

This PR implements a new data enhancement to...

with the #894 loglevel controller has merged, we can remove the loglevel in manifests, which now is already controlled by loglevel controller and is set on Normal by default

Categories

  • Bugfix
  • Data Enhancement
  • Feature
  • Backporting
  • Others (CI, Infrastructure, Documentation)

Sample Archive

  • path/to/sample_data.json

Documentation

  • path/to/documentation.md

Unit Tests

  • path/to/file_test.go

Privacy

Yes. There are no sensitive data in the newly collected information.

Changelog

Breaking Changes

Yes/No

References

https://issues.redhat.com/browse/???
https://access.redhat.com/solutions/???

Signed-off-by: lan.tian <lance5890@163.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 23, 2024
@openshift-ci-robot
Copy link
Contributor

@lance5890: This pull request explicitly references no jira issue.

In response to this:

This PR implements a new data enhancement to...

with the #894 loglevel controller has merged, we can remove the loglevel in manifests, which now is already controlled by loglevel controller and is set on Normal by default

Categories

  • Bugfix
  • Data Enhancement
  • Feature
  • Backporting
  • Others (CI, Infrastructure, Documentation)

Sample Archive

  • path/to/sample_data.json

Documentation

  • path/to/documentation.md

Unit Tests

  • path/to/file_test.go

Privacy

Yes. There are no sensitive data in the newly collected information.

Changelog

Breaking Changes

Yes/No

References

https://issues.redhat.com/browse/???
https://access.redhat.com/solutions/???

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from ncaak and rluders January 23, 2024 01:20
@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jan 23, 2024
Copy link

openshift-ci bot commented Jan 23, 2024

Hi @lance5890. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@lance5890
Copy link
Contributor Author

/cc @tremes

@openshift-ci openshift-ci bot requested a review from tremes January 23, 2024 01:23
@tremes
Copy link
Contributor

tremes commented Jan 30, 2024

/ok-to-test
/approve

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jan 30, 2024
Copy link

openshift-ci bot commented Jan 30, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lance5890, tremes

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 Jan 30, 2024
@lance5890
Copy link
Contributor Author

/retest-required

@tremes
Copy link
Contributor

tremes commented Jan 30, 2024

@lance5890 we will need to either udpate/fix our tests or update the log level of some corresponding messages. Do you know what the default level (from the https://github.com/openshift/api/blob/master/operator/v1/types.go#L65) is equal to in terms of klog level https://github.com/kubernetes/klog/blob/main/klog.go#L1365?

@lance5890
Copy link
Contributor Author

lance5890 commented Jan 31, 2024

we will need to either udpate/fix our tests or update the log level of some corresponding messages. Do you know what the default level (from the https://github.com/openshift/api/blob/master/operator/v1/types.go#L65) is equal to in terms of klog level https://github.com/kubernetes/klog/blob/main/klog.go#L1365?

maybe u can read this https://github.com/openshift/library-go/blob/2ad786549f07f264339f63b12b71a0fe5e77e832/pkg/operator/loglevel/util.go#L14-L27

the default operator loglevel is Normal, which is eqaul to v(2)

@lance5890
Copy link
Contributor Author

/retest-required

1 similar comment
@lance5890
Copy link
Contributor Author

/retest-required

@tremes
Copy link
Contributor

tremes commented Jan 31, 2024

@lance5890 stop retesting please. We need to update the tests first as mentioned above.

@tremes
Copy link
Contributor

tremes commented Feb 2, 2024

/retest

@JoaoFula
Copy link
Contributor

JoaoFula commented Feb 2, 2024

/label qe-approved

@tremes
Copy link
Contributor

tremes commented Feb 2, 2024

/test insights-operator-e2e-tests

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Feb 2, 2024
@lance5890
Copy link
Contributor Author

/test insights-operator-e2e-tests

5 similar comments
@lance5890
Copy link
Contributor Author

/test insights-operator-e2e-tests

@tremes
Copy link
Contributor

tremes commented Feb 5, 2024

/test insights-operator-e2e-tests

@lance5890
Copy link
Contributor Author

/test insights-operator-e2e-tests

@lance5890
Copy link
Contributor Author

/test insights-operator-e2e-tests

@tremes
Copy link
Contributor

tremes commented Feb 15, 2024

/test insights-operator-e2e-tests

@tremes
Copy link
Contributor

tremes commented Feb 15, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 15, 2024
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 9834810 and 2 for PR HEAD 51cb302 in total

Copy link

openshift-ci bot commented Feb 16, 2024

@lance5890: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit ac7704e into openshift:master Feb 16, 2024
9 checks passed
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-insights-operator-container-v4.16.0-202402160210.p0.gac7704e.assembly.stream.el9 for distgit ose-insights-operator.
All builds following this will include this PR.

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. 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. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants