apiserver stopped

[naser71]

What Happened?

Hi:

I was following the link https://docs.tigera.io/calico/latest/getting-started/kubernetes/vpp/getting-started to install calico-vpp and after I followed the the Required Configuration section by changing the uplinkinterfaces: interfacename to the Ubuntu interface name then changed this interface IP address to be same as the Kubernetes node IP address, the apiserver stopped.

In the "calico-vpp.yaml" file, I changed the below section :
CALICOVPP_INTERFACES: |-
{
"uplinkInterfaces": [ { "interfaceName": "eth0" } ]

To:

CALICOVPP_INTERFACES: |-
{
"uplinkInterfaces": [ { "interfaceName": "ens37" } ]

ens37 is an interface in Ubuntu. Then I changed this interface IP address to be same as the Kubernetes controller node IP address. (That's what I understood from this Required Configuration section)
After that the apiserver stopped.
I shutdown Minikube and started it again but I got the below error message:

naser@naser:~$ minikube start

• [thesis1] minikube v1.30.1 on Ubuntu 22.04
• Using the virtualbox driver based on existing profile
• Starting control plane node thesis1 in cluster thesis1
• Restarting existing virtualbox VM for "thesis1" ...
  ! StartHost failed, but will try again: driver start: Error setting up host only network on machine start: host-only cidr conflicts with the network address of a host interface
• Restarting existing virtualbox VM for "thesis1" ...
• Failed to start virtualbox VM. Running "minikube delete -p thesis1" may fix it: driver start: Error setting up host only network on machine start: host-only cidr conflicts with the network address of a host interface

X Exiting due to IF_HOST_CIDR_CONFLICT: Failed to start host: driver start: Error setting up host only network on machine start: host-only cidr conflicts with the network address of a host interface

• Suggestion: Specify an alternate --host-only-cidr value, such as 172.16.0.1/24
• Related issue: host-only cidr conflicts with the network address of a host interface #3594

Attach the log file

calico-vpp-yaml.txt
log.txt

Operating System

Ubuntu

Driver

VirtualBox

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[k8s-triage-robot]

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

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

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

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.