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

hyperkit integration testing: could not find an IP address / OS type not recognized #5368

Closed
tstromberg opened this issue Sep 16, 2019 · 1 comment
Labels
co/hyperkit Hyperkit related issues help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/flake Categorizes issue or PR as related to a flaky test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@tstromberg
Copy link
Contributor

tstromberg commented Sep 16, 2019

This error has been popping up more frequently:

cluster.go:94] Provisioning machine with config: {KeepContext:false EmbedCerts:false MinikubeISO:https://storage.googleapis.com/minikube/iso/minikube-v1.4.0-beta.2.iso Memory:2000 CPUs:2 DiskSize:20000 VMDriver:hyperkit ContainerRuntime:docker HyperkitVpnKitSock: HyperkitVSockPorts:[] DockerEnv:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:192.168.99.1/24 HypervVirtualSwitch: KVMNetwork:default KVMQemuURI:qemu:///system KVMGPU:false KVMHidden:false Downloader:{} DockerOpt:[] DisableDriverMounts:false NFSShare:[] NFSSharesRoot:/nfsshares UUID: NoVTXCheck:false DNSProxy:false HostDNSResolver:true}
start.go:838] StartHost: create: Error creating machine: Error in driver during machine creation: IP address never found in dhcp leases file Temporary error: could not find an IP address for 7e:f:4e:c2:cb:dd
cluster.go:98] Skipping create...Using existing machine configuration
cluster.go:117] Machine state:  Running
cluster.go:135] engine options: &{ArbitraryFlags:[] DNS:[] GraphDir: Env:[] Ipv6:false InsecureRegistry:[10.96.0.0/12] Labels:[] LogLevel: StorageDriver: SelinuxEnabled:false TLSVerify:false RegistryMirror:[] InstallURL:https://get.docker.com}
cluster.go:156] configureHost: &{plugin:0xc000800230 heartbeatDoneCh:0xc000040d20 Client:0xc00016f7d0}
cluster.go:178] Configuring auth for driver hyperkit ...
cluster.go:158] configureHost completed within 6m7.361143537s
start.go:838] StartHost: Temporary Error: Error configuring auth on host: OS type not recognized

Example: https://storage.googleapis.com/minikube-builds/logs/5354/HyperKit_macOS.txt

I suspect that hyperkit has race conditions when run in parallel. It's difficult to tell at the current level of debugging. It's worth noting that we currently wait up to a minute for the IP to appear, which should be more than enough.

@tstromberg tstromberg added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/flake Categorizes issue or PR as related to a flaky test. labels Sep 16, 2019
@tstromberg tstromberg added this to the v1.5.0-candidate milestone Sep 16, 2019
@tstromberg tstromberg added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Sep 16, 2019
@tstromberg
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/hyperkit Hyperkit related issues help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/flake Categorizes issue or PR as related to a flaky test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

1 participant