Visitar URL original
improve UI advice when user needs to delete the cluster · Issue #10460 · kubernetes/minikube · GitHub
Skip to content

improve UI advice when user needs to delete the cluster #10460

Open
Open
improve UI advice when user needs to delete the cluster#10460
Assignees
BrinthaSivakamiakstron
Labels
good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.kind/bugCategorizes issue or PR as related to a bug.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/backlogHigher priority than priority/awaiting-more-evidence.

Description

@medyagh
medyagh
opened on Feb 12, 2021

here we confuse the user with two things

❗ You cannot change the memory size for an exiting minikube cluster. Please first delete the cluster.
and

😿 Failed to start ssh bare metal machine. Running "minikube delete -p foo" may fix it: config: please provide an IP address

we should had sticked with first advice

drewpca(pts/0):~% minikube start -p foo --memory 6GB
😄  [foo] minikube v1.17.1 on Debian rodete
✨  Using the ssh driver based on existing profile
❗  You cannot change the memory size for an exiting minikube cluster. Please first delete the cluster.
👍  Starting control plane node foo in cluster foo
🤦  StartHost failed, but will try again: config: please provide an IP address
😿  Failed to start ssh bare metal machine. Running "minikube delete -p foo" may fix it: config: please provide an IP address
 
❌  Exiting due to GUEST_PROVISION: Failed to start host: config: please provide an IP address
 
😿  If the above advice does not help, please let us know: 
👉  https://github.com/kubernetes/minikube/issues/new/choose

Activity

  1. medyagh
    added
    good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.
    kind/bugCategorizes issue or PR as related to a bug.
    priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.
    on Feb 12, 2021

  2. BLasan commented on Feb 13, 2021

    @BLasan
    BLasan
    on Feb 13, 2021
    Contributor

    @medyagh You mean we do not need the log Failed to start ssh bare metal machine. Running "minikube delete -p foo" may fix it: config: please provide an IP address right? I would like to open a PR for this

  3. BLasan commented on Feb 13, 2021

    @BLasan
    BLasan
    on Feb 13, 2021
    Contributor

    /assign

  4. k8s-ci-robot
    assigned
    BLasan
    on Feb 13, 2021

  5. BLasan commented on Feb 20, 2021

    @BLasan
    BLasan
    on Feb 20, 2021
    Contributor

    @medyagh btw I forgot to add the output I received after running the command without the changes done in #10473

    minikube start -p foo --memory 3GB
😄  [foo] minikube v1.17.1 on Ubuntu 20.04
✨  Using the docker driver based on existing profile
❗  You cannot change the memory size for an exiting minikube cluster. Please first delete the cluster.
👍  Starting control plane node foo in cluster foo
🔄  Restarting existing docker container for "foo" ...
🐳  Preparing Kubernetes v1.20.2 on Docker 20.10.2 ...
🔎  Verifying Kubernetes components...
    ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v4
🌟  Enabled addons: storage-provisioner, default-storageclass
🏄  Done! kubectl is now configured to use "foo" cluster and "default" namespace by default

    I was not getting errors below

    🤦  StartHost failed, but will try again: config: please provide an IP address
😿  Failed to start ssh bare metal machine. Running "minikube delete -p foo" may fix it: config: please provide an IP address
  6. spowelljr
    added
    priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.
    and removed
    priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.
    on Apr 7, 2021

  7. rahulii commented on May 30, 2021

    @rahulii
    rahulii
    on May 30, 2021

    /assign
    I would like to give it a shot. Just wanted to know where should i begin searching the code!
    /cc @medyagh

  8. k8s-ci-robot
    assigned
    rahulii
    on May 30, 2021

  9. k8s-triage-robot commented on Aug 28, 2021

    @k8s-triage-robot
    k8s-triage-robot
    on Aug 28, 2021

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

    This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
    • Mark this issue or PR as rotten with /lifecycle rotten
    • Close this issue or PR with /close
    • Offer to help out with Issue Triage

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

    /lifecycle stale

  10. k8s-ci-robot
    added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Aug 28, 2021

  11. k8s-triage-robot commented on Sep 27, 2021

    @k8s-triage-robot
    k8s-triage-robot
    on Sep 27, 2021

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

    This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
    • Close this issue or PR with /close
    • Offer to help out with Issue Triage

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

    /lifecycle rotten

  12. k8s-ci-robot
    removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Sep 27, 2021

  13. 16 remaining items

  14. spowelljr
    unassigned
    e-tienne
    on Mar 24, 2022

  15. spowelljr commented on Mar 24, 2022

    @spowelljr
    spowelljr
    on Mar 24, 2022
    Member

    @e-tienne Are you still working on this? I unassigned this task from you, but if you are actively working on it please reassign yourself, thanks!

  16. maknop commented on Jun 9, 2022

    @maknop
    maknop
    on Jun 9, 2022

    /assign

  17. k8s-ci-robot
    assigned
    maknop
    on Jun 9, 2022

  18. maknop commented on Jun 9, 2022

    @maknop
    maknop
    on Jun 9, 2022

    Looks like this occurs when the driver is set to ssh. I'm going to give this issue a try. 😄

  19. maknop
    removed their assignment
    on Jul 24, 2022

  20. BrinthaSivakami commented on Sep 3, 2022

    @BrinthaSivakami
    BrinthaSivakami
    on Sep 3, 2022

    /assign

  21. k8s-ci-robot
    assigned
    BrinthaSivakami
    on Sep 3, 2022

  22. akstron commented on Jun 7, 2023

    @akstron
    akstron
    on Jun 7, 2023

    /assign

  23. k8s-ci-robot
    assigned
    akstron
    on Jun 7, 2023

  24. akstron commented on Jun 7, 2023

    @akstron
    akstron
    on Jun 7, 2023

    In contrast to the discussion here: #10460 (comment), I found that the first statement was not because of deletion and recreation of the cluster.
    The call stack between the two statement is pretty large, so passing a flag seems difficult. What I suggest is removing the below line from the 2nd statement.
    Running "minikube delete -p foo" may fix it

  25. allengitworld20 commented on Sep 23, 2026

    @allengitworld20
    allengitworld20
    on Sep 23, 2026

    /assign

  26. kubernetes-prow
    assigned
    allengitworld20
    on Sep 23, 2026

  27. allengitworld20 commented on Sep 23, 2026

    @allengitworld20
    allengitworld20
    on Sep 23, 2026

    /unassign

  28. kubernetes-prow
    unassigned
    allengitworld20
    on Sep 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.kind/bugCategorizes issue or PR as related to a bug.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/backlogHigher priority than priority/awaiting-more-evidence.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions