minikube logs not outputing to file when using --last-start-only #19931

mattisafur · 2024-11-10T15:45:44Z

What Happened?

When running minikube logs --file log.txt --last-start-only output is printer to the terminal and an empty file is created.

output of minikube logs --file log.txt --last-start-only --alsologtostderr:

I1110 17:39:34.383805   16647 out.go:345] Setting OutFile to fd 1 ...
I1110 17:39:34.383994   16647 out.go:358] Setting ErrFile to fd 2...
I1110 17:39:34.384149   16647 root.go:338] Updating PATH: /home/<username>/.minikube/bin
I1110 17:39:34.392920   16647 out.go:177]

I1110 17:39:34.400630   16647 out.go:177] ==> Last Start <==
==> Last Start <==
I1110 17:39:34.419332   16647 out.go:177] Log file created at: 2024/11/10 17:12:27
Running on machine: <hostname>
Binary: Built with gc go1.22.5 for linux/amd64
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
I1110 17:12:27.286943   16010 out.go:345] Setting OutFile to fd 1 ...
I1110 17:12:27.287120   16010 out.go:358] Setting ErrFile to fd 2...
I1110 17:12:27.287271   16010 root.go:338] Updating PATH: /home/<username>/.minikube/bin

Log file created at: 2024/11/10 17:12:27
Running on machine: <hostname>
Binary: Built with gc go1.22.5 for linux/amd64
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
I1110 17:12:27.286943   16010 out.go:345] Setting OutFile to fd 1 ...
I1110 17:12:27.287120   16010 out.go:358] Setting ErrFile to fd 2...
I1110 17:12:27.287271   16010 root.go:338] Updating PATH: /home/<username>/.minikube/bin

Tested on Ubuntu running on WSL with docker driver.

output of minikube version:

minikube version: v1.34.0
commit: 210b148df93a80eb872ecbeb7e35281b3c582c61

Attach the log file

Log file is not attached as the file does not contain any information about the logs command.

Operating System

Ubuntu

Driver

Docker

The text was updated successfully, but these errors were encountered:

Ritikaa96 · 2024-12-11T07:38:43Z

In my case the --last-start-only addition end up giving empty file.
with minikube logs -f=log.txt i can see logs being added there.

mattisafur · 2024-12-11T18:02:43Z

with minikube logs -f=log.txt i can see logs being added there.

couldn't quite get what you mean, -f is a shorthand for --follow. I'm guessing you mean --file=filename? in that case I agree, the issue is only present if --last-start-only is added, though I still haven't checked it with other flags added.

I suspect it's just just an issue with --last-start-only overriding the --file flag and causing the output to still go to stdout instead of a file. I'll have to check the code to verify that, but I don't have the time for it at the moment...

Ritikaa96 · 2024-12-17T10:55:39Z

Hi @mattisafur Just for reference, this is the implementation of the flag --last-start-only: https://github.com/kubernetes/minikube/blob/master/cmd/minikube/cmd/logs.go#L80
If i find something regarding over-riding the --file flag i'll inform here

mattisafur · 2024-12-17T14:31:59Z

I looked at the implementation. at the moment it does the following (when --file is set):

flowchart

A{--last-start-only set?} --> |true| B[print start log to stdout]
A --> |false| C
C{--audit set?} --> |true| D[print audit log to stdout]
C --> |false| E[print both audit log and last start log to file]

It makes more sense to me that will will work based on these rules:

if --file <filepath> is specified, output to file instead of stdout
if --audit is specified, output only the audit log
if --last-start-only is specified, output only the last-start log

(handle a case where both --audit and --last-start-only are specified? maybe just output nothing?)

I'll make a PR for this change.

k8s-triage-robot · 2025-03-17T15:31:45Z

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot · 2025-04-16T16:26:37Z

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot · 2025-05-16T17:03:35Z

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue with /reopen
Mark this issue as fresh with /remove-lifecycle rotten
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot · 2025-05-16T17:03:41Z

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied

After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue with /reopen

Mark this issue as fresh with /remove-lifecycle rotten

Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.

mattisafur added a commit to mattisafur/minikube that referenced this issue Dec 20, 2024

fixed logs issue kubernetes#19931

c1bbbb9

mattisafur mentioned this issue Dec 20, 2024

fixed logs issue #19931 #20138

Open

mattisafur added a commit to mattisafur/minikube that referenced this issue Jan 7, 2025

fixed logs issue kubernetes#19931

58aadf1

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 17, 2025

k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 16, 2025

k8s-ci-robot closed this as not planned Won't fix, can't repro, duplicate, stale May 16, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

minikube logs not outputing to file when using --last-start-only #19931

minikube logs not outputing to file when using --last-start-only #19931

mattisafur commented Nov 10, 2024

Ritikaa96 commented Dec 11, 2024

Uh oh!

mattisafur commented Dec 11, 2024 •

edited

Loading

Uh oh!

Ritikaa96 commented Dec 17, 2024

Uh oh!

mattisafur commented Dec 17, 2024 •

edited

Loading

Uh oh!

k8s-triage-robot commented Mar 17, 2025

Uh oh!

k8s-triage-robot commented Apr 16, 2025

Uh oh!

k8s-triage-robot commented May 16, 2025

Uh oh!

k8s-ci-robot commented May 16, 2025

Uh oh!

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

minikube logs not outputing to file when using --last-start-only #19931

minikube logs not outputing to file when using --last-start-only #19931

Comments

mattisafur commented Nov 10, 2024

What Happened?

Attach the log file

Operating System

Driver

Ritikaa96 commented Dec 11, 2024

Uh oh!

mattisafur commented Dec 11, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Ritikaa96 commented Dec 17, 2024

Uh oh!

mattisafur commented Dec 17, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

k8s-triage-robot commented Mar 17, 2025

Uh oh!

k8s-triage-robot commented Apr 16, 2025

Uh oh!

k8s-triage-robot commented May 16, 2025

Uh oh!

k8s-ci-robot commented May 16, 2025

Uh oh!

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

mattisafur commented Dec 11, 2024 •

edited

Loading

mattisafur commented Dec 17, 2024 •

edited

Loading