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

kubernet #19801

Open
nuzeleke opened this issue Oct 14, 2024 · 3 comments
Open

kubernet #19801

nuzeleke opened this issue Oct 14, 2024 · 3 comments
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@nuzeleke
Copy link

What Happened?

❌ Exiting due to K8S_INSTALL_FAILED: Failed to update cluster: update primary control-plane node: downloading binaries: downloading kubectl: download failed: https://dl.k8s.io/release/v1.31.0/bin/linux/amd64/kubectl?checksum=file:https://dl.k8s.io/release/v1.31.0/bin/linux/amd64/kubectl.sha256: getter: &{Ctx:context.Background Src:https://dl.k8s.io/release/v1.31.0/bin/linux/amd64/kubectl?checksum=file:https://dl.k8s.io/release/v1.31.0/bin/linux/amd64/kubectl.sha256 Dst:/home/ng/.minikube/cache/linux/amd64/v1.31.0/kubectl.download Pwd: Mode:2 Umask:---------- Detectors:[0x4eb7820 0x4eb7820 0x4eb7820 0x4eb7820 0x4eb7820 0x4eb7820 0x4eb7820] Decompressors:map[bz2:0xc0004aede0 gz:0xc0004aede8 tar:0xc0004aed60 tar.bz2:0xc0004aed80 tar.gz:0xc0004aeda0 tar.xz:0xc0004aedb0 tar.zst:0xc0004aedd0 tbz2:0xc0004aed80 tgz:0xc0004aeda0 txz:0xc0004aedb0 tzst:0xc0004aedd0 xz:0xc0004aee00 zip:0xc0004aee20 zst:0xc0004aee08] Getters:map[file:0xc001d95970 http:0xc00164cc80 https:0xc00164ccd0] Dir:false ProgressListener:0x4e44750 Insecure:false DisableSymlinks:false Options:[0x12e5e60]}: invalid checksum: Error downloading checksum file: Get "https://dl.k8s.io/release/v1.31.0/bin/linux/amd64/kubectl.sha256": dial tcp [2600:1901:0:26f3::]:443: connect: network is unreachable

Attach the log file

❌ Exiting due to K8S_INSTALL_FAILED: Failed to update cluster: update primary control-plane node: downloading binaries: downloading kubectl: download failed: https://dl.k8s.io/release/v1.31.0/bin/linux/amd64/kubectl?checksum=file:https://dl.k8s.io/release/v1.31.0/bin/linux/amd64/kubectl.sha256: getter: &{Ctx:context.Background Src:https://dl.k8s.io/release/v1.31.0/bin/linux/amd64/kubectl?checksum=file:https://dl.k8s.io/release/v1.31.0/bin/linux/amd64/kubectl.sha256 Dst:/home/ng/.minikube/cache/linux/amd64/v1.31.0/kubectl.download Pwd: Mode:2 Umask:---------- Detectors:[0x4eb7820 0x4eb7820 0x4eb7820 0x4eb7820 0x4eb7820 0x4eb7820 0x4eb7820] Decompressors:map[bz2:0xc0004aede0 gz:0xc0004aede8 tar:0xc0004aed60 tar.bz2:0xc0004aed80 tar.gz:0xc0004aeda0 tar.xz:0xc0004aedb0 tar.zst:0xc0004aedd0 tbz2:0xc0004aed80 tgz:0xc0004aeda0 txz:0xc0004aedb0 tzst:0xc0004aedd0 xz:0xc0004aee00 zip:0xc0004aee20 zst:0xc0004aee08] Getters:map[file:0xc001d95970 http:0xc00164cc80 https:0xc00164ccd0] Dir:false ProgressListener:0x4e44750 Insecure:false DisableSymlinks:false Options:[0x12e5e60]}: invalid checksum: Error downloading checksum file: Get "https://dl.k8s.io/release/v1.31.0/bin/linux/amd64/kubectl.sha256": dial tcp [2600:1901:0:26f3::]:443: connect: network is unreachable

Operating System

Ubuntu

Driver

VirtualBox

@medyagh
Copy link
Member

medyagh commented Oct 21, 2024

Thank you for sharing your experience! If you don't mind, could you provide minikube logs ?

Please attach (drag) thelogs.txt file to this issue which can be generated by running this command:

$ minikube logs --file=logs.txt

This will help us isolate the problem further. Thank you!

/triage needs-information
/kind support

@k8s-ci-robot k8s-ci-robot added triage/needs-information Indicates an issue needs more information in order to work on it. kind/support Categorizes issue or PR as a support question. labels Oct 21, 2024
@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 19, 2025
@k8s-triage-robot
Copy link

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-ci-robot 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 Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

4 participants