using a profile with hyperkit hangs: failed to get node info: node "minikube" not found #3103
Labels
area/profiles
issues related to profile handling
co/hyperkit
Hyperkit related issues
ev/apiserver-refused
failures due to the master on 8443 returning "Connection Refused"
ev/hung-start
kind/bug
Categorizes issue or PR as related to a bug.
triage/obsolete
Bugs that no longer occur in the latest stable release
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
Please provide the following details:
Environment:
What happened:
As the title says, minikube with
--vm-driver hyperkit
and non-default profile won't start. The initialisation process gets stuck at:What you expected to happen:
Expected a successful initialisation.
How to reproduce it (as minimally and precisely as possible):
minikube start --profile test.minikube.local --vm-driver hyperkit
Output of
minikube logs
(if applicable):No other output really.
The text was updated successfully, but these errors were encountered: