Ability to change calico IP_AUTODETECTION_METHOD

Bug #2065241 reported by Hemanth Nakkina
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Snap
New
Undecided
Unassigned

Bug Description

sunbeam 2024.1/edge installed on a machine with following network configuration failed in starting calico-node pod

                  +------------+
                   | br-api (openvswitch) |
                   | 192.168.20.X/24
                   | Gateway: 192.168.20.1
                   | DNS: 10.0.0.1, 10.0.0.2
                   | Interfaces: bond0.20
                   +------------+
                           |
                           |
                   +------------+
                   | br-floating (openvswitch) |
                   | Interfaces: bond0.21
                   | 192.168.21.X/24 (for public network but NO IP associated to this bridge)
                   +------------+
                           |
                           |
                   +------------+
                   | br-mgm (openvswitch) |
                   | 192.168.2.X/24
                   | DNS: 192.168.2.3, 192.168.2.4, 192.168.2.5
                   | Interfaces: eno1
                   +------------+
                           |
                           |
                   +------------+
                   | br-stor (openvswitch) |
                   | 192.168.31.X/24
                   | DNS: 192.168.31.2, 192.168.31.4, 192.168.31.5
                   | Interfaces: bond1.31
                   +------------+
                           |
                           |
                   +------------+
                   | bond0 |
                   | Interfaces: enp129s0f0np0, enp225s0f0np0
                   +------------+
                           |
                           |
                   +------------+
                   | bond1 |
                   | Interfaces: enp129s0f1np1, enp225s0f1np1
                   +------------+
                           |

calico-node logs:
sudo microk8s.kubectl -n kube-system logs calico-node-rbf2z
Defaulted container "calico-node" out of: calico-node, upgrade-ipam (init), install-cni (init)
2024-05-08 09:36:38.841 [INFO][9] startup/startup.go 427: Early log level set to info
2024-05-08 09:36:38.841 [INFO][9] startup/utils.go 126: Using NODENAME environment for node name node-01
2024-05-08 09:36:38.841 [INFO][9] startup/utils.go 138: Determined node name: node-01
2024-05-08 09:36:38.841 [INFO][9] startup/startup.go 94: Starting node node-01 with version v3.25.1
2024-05-08 09:36:38.842 [INFO][9] startup/startup.go 432: Checking datastore connection
2024-05-08 09:36:38.850 [INFO][9] startup/startup.go 456: Datastore connection verified
2024-05-08 09:36:38.850 [INFO][9] startup/startup.go 104: Datastore is ready
2024-05-08 09:36:38.853 [INFO][9] startup/customresource.go 102: Error getting resource Key=GlobalFelixConfig(name=CalicoVersion) Name="calicoversion" Resource="GlobalFelixConfigs" error=the server could not find the requested resource (get GlobalFelixConfigs.crd.projectcalico.org calicoversion)
2024-05-08 09:36:38.862 [INFO][9] startup/startup.go 485: Initialize BGP data
2024-05-08 09:36:38.864 [WARNING][9] startup/autodetection_methods.go 99: Unable to auto-detect an IPv4 address: no valid IPv4 addresses found on the host interfaces
2024-05-08 09:36:38.864 [WARNING][9] startup/startup.go 507: Couldn't autodetect an IPv4 address. If auto-detecting, choose a different autodetection method. Otherwise provide an explicit address.
2024-05-08 09:36:38.864 [INFO][9] startup/startup.go 391: Clearing out-of-date IPv4 address from this node IP=""
2024-05-08 09:36:38.872 [WARNING][9] startup/utils.go 48: Terminating
Calico node failed to start

From logs, you can see calico-node is not able to autodetect any IPv4 address

Updating IP_AUTODETECTION_METHOD to use specific interface made it work

$ cat /var/snap/microk8s/current/args/cni-network/cni.yaml | grep br-api
              value: "interface=br-api"

User should be able to configure this setting in sunbeam.

Reference: Discussion in user forum https://discourse.ubuntu.com/t/manage-a-proxied-environment/43946/9

description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.