kubernetes/minikube

Command start should delete node with empty ip or retrieve one

Open

#9,834 opened on Dec 3, 2020

View on GitHub
 (17 comments) (0 reactions) (0 assignees)Go (5,222 forks)batch import
co/multinodehelp wantedkind/buglifecycle/stalepriority/important-longterm

Repository metrics

Stars
 (31,799 stars)
PR merge metrics
 (Avg merge 12d 19h) (43 merged PRs in 30d)

Description

Steps to reproduce the issue:

  1. Open config.json, run minikube node add minikube-m02
  2. Interrupt the add command after the node info presented in config.json but before ip is set
  3. Run minikube stop && minikube start, the node couldn't start

Contributor guide

Research direction
Investigate the node addition interruption and ensure the start command handles nodes with empty IP.
Tech stack
go
Domain
backenddevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Gominikube
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75