Skip to content

Conversation

@tmshort
Copy link
Contributor

@tmshort tmshort commented Apr 15, 2025

Cherry-pick of upstream PR 1918

Some log levels were defaultLogLevel+1 (5), change those to defaultLogLevel (4)

Signed-off-by: Todd Short tshort@redhat.com
(cherry picked from commit 2f22dcf)

Cherry-pick of upstream PR 1918

Some log levels were defaultLogLevel+1 (5), change those to defaultLogLevel (4)

Signed-off-by: Todd Short <tshort@redhat.com>
(cherry picked from commit 2f22dcf)
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 15, 2025
@openshift-ci-robot
Copy link

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

In response to this:

Cherry-pick of upstream PR 1918

Some log levels were defaultLogLevel+1 (5), change those to defaultLogLevel (4)

Signed-off-by: Todd Short tshort@redhat.com
(cherry picked from commit 2f22dcf)

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 anik120 and bentito April 15, 2025 19:51
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 15, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 15, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 15, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: grokspawn, tmshort

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

@joelanford
Copy link
Member

/lgtm
/approval

@openshift-merge-bot openshift-merge-bot bot merged commit 209ff44 into openshift:main Apr 15, 2025
9 of 11 checks passed
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 15, 2025

@tmshort: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/openshift-e2e-aws-techpreview 3bd5eaf link false /test openshift-e2e-aws-techpreview

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-sigs/prow repository. I understand the commands that are listed here.

@tmshort tmshort deleted the update-log-levels branch April 16, 2025 03:26
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-olm-catalogd
This PR has been included in build ose-olm-catalogd-container-v4.19.0-202504160315.p0.g209ff44.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-olm-operator-controller
This PR has been included in build ose-olm-operator-controller-container-v4.19.0-202504160315.p0.g209ff44.assembly.stream.el9.
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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants