Increase timeout for creating IP address for KVM by 1m

[nikimanoledaki]

Fixes #3566

Starting minikube with KVM with minikube start --driver=kvm2 returned this error consistently:

😿  Failed to start kvm2 VM. Running "minikube delete" may fix it: creating host: create: Error creating machine: Error in driver during machine creation: IP not available after waiting: machine minikube didn't return IP after 1 minute

❌  Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: Error creating machine: Error in driver during machine creation: IP not available after waiting: machine minikube didn't return IP after 1 minute

The suggestions in #3566 (e.g. firewall changes, sudo systemctl restart libvirtd.service) did not fix the issue for me.

DHCP did not have enough time to throw an IP. This is the result immediately after minikube start --driver=kvm2 timed out:

virsh net-dhcp-leases mk-minikube
 Expiry Time   MAC address   Protocol   IP address   Hostname   Client ID or DUID
-----------------------------------------------------------------------------------

A few seconds later, an IP address was provided:

virsh net-dhcp-leases mk-minikube
 Expiry Time           MAC address         Protocol   IP address         Hostname   Client ID or DUID
----------------------------------------------------------------------------------------------------------
 2022-09-16 09:23:31   52:54:00:ca:cc:bd   ipv4       192.168.39.60/24   minikube   01:52:54:00:ca:cc:bd

Validation that virbr1 has an address:

arp -e
Address                  HWtype  HWaddress           Flags Mask            Iface
10.0.2.3                 ether   52:54:00:12:35:03   C                     eth0
192.168.122.124          ether   52:54:00:5e:79:f7   C                     virbr0
192.168.39.134           ether   52:54:00:be:1c:2a   C                     virbr1
_gateway                 ether   52:54:00:12:35:02   C                     eth0

Increasing the timeout to 2m and trying again fixed the issue! DHCP needed more time to resolve.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: nikimanoledaki / name: Niki (a539d51)

[k8s-ci-robot]

Welcome @nikimanoledaki!

It looks like this is your first PR to kubernetes/minikube 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/minikube has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @nikimanoledaki. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: nikimanoledaki
Once this PR has been reviewed and has the lgtm label, please assign afbjorklund for approval by writing /assign @afbjorklund in a comment. For more information see:The Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[minikube-bot]

Can one of the admins verify this patch?