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

[BUG] supportbundle/kubelet.log empty in k3s environment #7121

Closed
yangchiu opened this issue Nov 16, 2023 · 5 comments
Closed

[BUG] supportbundle/kubelet.log empty in k3s environment #7121

yangchiu opened this issue Nov 16, 2023 · 5 comments
Assignees
@c3y1huang @chriscchien
Labels
area/support-bundle Support bundle for troubleshooting area/troubleshoot Troubleshoot related backport/1.4.5 backport/1.5.4 kind/bug
Milestone
v1.6.0

Comments

@yangchiu
Copy link
Member

Describe the bug (🐛 if you encounter this issue)

collect_kubelet_log function in support-bundle-kit package doesn't support k3s, so the kubelet.log is always empty in k3s environment.

Since in our daily regression uses k3s by default, which makes it difficult to get kubelet related information in daily debugging.

To Reproduce

Expected behavior

Support bundle for troubleshooting

Environment

  • Longhorn version:
  • Installation method (e.g. Rancher Catalog App/Helm/Kubectl):
  • Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:
    • Number of management node in the cluster:
    • Number of worker node in the cluster:
  • Node config
    • OS type and version:
    • Kernel version:
    • CPU per node:
    • Memory per node:
    • Disk type(e.g. SSD/NVMe/HDD):
    • Network bandwidth between the nodes:
  • Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
  • Number of Longhorn volumes in the cluster:
  • Impacted Longhorn resources:
    • Volume names:

Additional context
@yangchiu yangchiu added this to the v1.6.0 milestone Nov 16, 2023
This was referenced Nov 16, 2023
Closed
Closed
@c3y1huang c3y1huang mentioned this issue Nov 16, 2023
Merged
@longhorn-io-github-bot
Copy link

longhorn-io-github-bot commented Nov 16, 2023 •
edited by c3y1huang
Loading

Pre Ready-For-Testing Checklist

  • Where is the reproduce steps/test steps documented?
    The reproduce steps/test steps are at:

  • Is there a workaround for the issue? If so, where is it documented?
    The workaround is at:

  • Does the PR include the explanation for the fix or the feature?

  • Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart?
    The PR for the YAML/chart change is at: fix(support-bundle): version bump #7118

  • Have the backend code been merged (Manager, Engine, Instance Manager, BackupStore etc) (including backport-needed/*)?
    The PR is at fix(collector-longhorn): k3s cluster missing kubelet log rancher/support-bundle-kit#84

  • Which areas/issues this PR might have potential impacts on?
    Area support-bundle, troubleshoot
    Issues

  • If labeled: require/LEP Has the Longhorn Enhancement Proposal PR submitted?
    The LEP PR is at

  • If labeled: area/ui Has the UI issue filed or ready to be merged (including backport-needed/*)?
    The UI issue/PR is at

  • If labeled: require/doc Has the necessary document PR submitted or merged (including backport-needed/*)?
    The documentation issue/PR is at

  • If labeled: require/automation-e2e Has the end-to-end test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue (including backport-needed/*)
    The automation skeleton PR is at
    The automation test case PR is at
    The issue of automation test case implementation is at (please create by the template)

  • If labeled: require/automation-engine Has the engine integration test been merged (including backport-needed/*)?
    The engine automation PR is at

  • If labeled: require/manual-test-plan Has the manual test plan been documented?
    The updated manual test plan is at test(manual): support bundle should include kubelet log when on K3s cluster longhorn-tests#1595

  • If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
    The compatibility issue is filed at

@c3y1huang c3y1huang added the area/troubleshoot Troubleshoot related label Nov 16, 2023
@c3y1huang c3y1huang mentioned this issue Nov 17, 2023
Merged
@c3y1huang
Copy link
Contributor

@yangchiu please help to mirror rancher/support-bundle-kit:v0.0.31 to longhornio, thank you.

@yangchiu
Copy link
Member Author

@yangchiu please help to mirror rancher/support-bundle-kit:v0.0.31 to longhornio, thank you.

done.

@c3y1huang c3y1huang mentioned this issue Nov 17, 2023
Merged
@chriscchien chriscchien self-assigned this Nov 20, 2023
@chriscchien
Copy link
Contributor

chriscchien commented Nov 20, 2023 •
edited
Loading

Verified pass in longhorn master (longhorn f67dd0) with test steps

Deploy Longhorn on k3s cluster and

  • In v1.5.3, support bundle have only kubelet.log in each node and the content is empty as below
-- No entries --
  • In longhorn master, support bundle has below file on each node as below
    • kubeket.log : -- No entries --
    • k3s-agent-service.log : Have kubelet log if the node is worker node
    • k3s-service.log : Have kubelet log if the node is control plane node

I will close this ticket if the manual test case merged, or test again if the test case updated, thank you

@chriscchien
Copy link
Contributor

Close this ticket as the doc merged without modify and test result pass, thank you.

@derekbit derekbit moved this to Closed in Longhorn Sprint Aug 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@c3y1huang c3y1huang

@chriscchien chriscchien

Labels
area/support-bundle Support bundle for troubleshooting area/troubleshoot Troubleshoot related backport/1.4.5 backport/1.5.4 kind/bug
Projects
Longhorn Sprint
Status: Closed
Milestone
v1.6.0
Development

No branches or pull requests
5 participants
@innobead @yangchiu @c3y1huang @longhorn-io-github-bot @chriscchien