Skip to content

Do not modify default logging parameters - #494

Merged
mangelajo merged 5 commits into
openshift:mainfrom
mangelajo:klog_fix
Jan 10, 2022
Merged

Do not modify default logging parameters#494
mangelajo merged 5 commits into
openshift:mainfrom
mangelajo:klog_fix

Conversation

@mangelajo

Copy link
Copy Markdown
Contributor

klog is a singleton library, and since we use that library from all
our services in a single process setting different log files won't
work, and will syphon all logs into the last log file we add.

Keep the simple strategy of letting all output to stderr for now.

Related-Issue: #493

Signed-off-by: Miguel Angel Ajo majopela@redhat.com

@mangelajo

Copy link
Copy Markdown
Contributor Author

@oglok @fzdarsky ^

@cooktheryan

Copy link
Copy Markdown
Contributor

/retest

@fzdarsky

Copy link
Copy Markdown
Contributor

@mangelajo this makes sense to me.

Would you recommend we also remove those from MicroShift itself for the time being?

@cooktheryan

Copy link
Copy Markdown
Contributor

/test verify

@mangelajo

Copy link
Copy Markdown
Contributor Author

Unit testing needs some looking: https://github.com/redhat-et/microshift/runs/4598372160?check_suite_focus=true#step:6:8

@oglok ^ can you have a look? , I'm looking into the cni/flannel rabbit-hole

@mangelajo

Copy link
Copy Markdown
Contributor Author

other than that it LGTM! :)

@oglok
oglok force-pushed the klog_fix branch 5 times, most recently from f98e971 to 99eca8d Compare December 22, 2021 16:53
@mangelajo

Copy link
Copy Markdown
Contributor Author

/lgtm

If it doesn't do what we expect we can always fix it

@openshift-ci

openshift-ci Bot commented Dec 22, 2021

Copy link
Copy Markdown
Contributor

@mangelajo: you cannot LGTM your own PR.

Details

In response to this:

/lgtm

If it doesn't do what we expect we can always fix it

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 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 22, 2021
@oglok

oglok commented Dec 22, 2021

Copy link
Copy Markdown
Contributor

/retest

@oglok

oglok commented Dec 22, 2021

Copy link
Copy Markdown
Contributor

/test e2e-openshift-conformance-sig-api-machinery

@fzdarsky

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Dec 22, 2021
@fzdarsky

Copy link
Copy Markdown
Contributor

/retest

@oglok

oglok commented Dec 22, 2021

Copy link
Copy Markdown
Contributor

/retest

mangelajo and others added 4 commits December 23, 2021 10:30
klog is a singleton library, and since we use that library from all
our services in a single process setting different log files won't
work, and will syphon all logs into the last log file we add.

Keep the simple strategy of letting all output to stderr for now.

Related-Issue: openshift#493

Signed-off-by: Miguel Angel Ajo <majopela@redhat.com>
  - vloglevel
  - vmodule
  - logtostderr
  - alsologtostderr

Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
@openshift-ci

openshift-ci Bot commented Dec 23, 2021

Copy link
Copy Markdown
Contributor

New changes are detected. LGTM label has been removed.

@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Dec 23, 2021
data = append(data, `
auditConfig:
auditFilePath: "` + cfg.LogDir + `/openshift-apiserver/audit.log"
auditFilePath: `+cfg.AuditLogDir+`openshift-apiserver-audit.log

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Suggested change
auditFilePath: `+cfg.AuditLogDir+`openshift-apiserver-audit.log
auditFilePath: "`+cfg.AuditLogDir+`openshift-apiserver-audit.log"

should we keep the commas?

Comment thread pkg/node/kube-proxy.go Outdated
Comment on lines +55 to +56
// Keeping the args in case something must be added in the future
args := []string{""}

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Suggested change
// Keeping the args in case something must be added in the future
args := []string{""}
// Keeping the args in case something must be added in the future
args := []string{}

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I wonder if this makes kubeproxy fail to start, empty arg in the arg list?

Locally we would not see it, because kubeproxy is internal, and already has configured all iptables, etc.

Comment thread test/config.yaml Outdated
Comment on lines 5 to 6
logVModule: microshift=4
logAlsotostderr: true

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

shall we remove those two?

Suggested change
logVModule: microshift=4
logAlsotostderr: true

Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
@oglok

oglok commented Dec 23, 2021

Copy link
Copy Markdown
Contributor

/retest

5 similar comments
@oglok

oglok commented Dec 23, 2021

Copy link
Copy Markdown
Contributor

/retest

@oglok

oglok commented Dec 23, 2021

Copy link
Copy Markdown
Contributor

/retest

@oglok

oglok commented Dec 23, 2021

Copy link
Copy Markdown
Contributor

/retest

@mangelajo

Copy link
Copy Markdown
Contributor Author

/retest

@oglok

oglok commented Dec 23, 2021

Copy link
Copy Markdown
Contributor

/retest

@mangelajo

Copy link
Copy Markdown
Contributor Author

xinx!!! ❇️

@mangelajo

Copy link
Copy Markdown
Contributor Author

/retest

1 similar comment
@cooktheryan

Copy link
Copy Markdown
Contributor

/retest

@mangelajo

Copy link
Copy Markdown
Contributor Author

/lgtm

@openshift-ci

openshift-ci Bot commented Jan 10, 2022

Copy link
Copy Markdown
Contributor

@mangelajo: you cannot LGTM your own PR.

Details

In response to this:

/lgtm

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 commented Jan 10, 2022

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fzdarsky, mangelajo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] As soon as one component starts logging to a file, all klog will sink into that file

4 participants