bottlerocket-os / bottlerocket-os/bottlerocket-core-kit

'Failed to parse network config' error when using net.toml with VMware Variant

Open
#429 13 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
34
Forks
77
Avg merge
2d 23h
Merged PRs (30d)
23

Description

**Image I'm using:**
vmware-k8s-1.24-v1.17.0

**What I expected to happen:**
Provide a `net.toml` file with the below contents, allowing the imaage to use static IP addressing to come online. I have also used `eno1` instead of the MAC address:

```
version = 3

["00:50:56:a6:8f:91".static4]
primary = true
enabled = true
addresses = ["10.0.0.156/22"]

[["00:50:56:a6:8f:91".route]]
to = "default"
via = "10.0.0.1"
route-metric = 100
```

**What actually happened:**
The OS fails to start up correctly, it fails with the following error message:
```
netdog[2212]: Unable to read/parse network config from '/var/lib/bottlerocket/net.toml': Failed to parse network config: data did not match any variant of untagged enum NetworkDeviceV1
```

**How to reproduce the problem:**
Spin up a VMware VM from the OVA. Use a live CD to add a `net.toml` file to the 12th partition with the contents above, assuming they are correct. Remove the CD and boot the VM.

It initially appears as if Bottlerocket can't find the network interface correctly, but as it happens so early in the boot process I'm not even sure how to troubleshoot this further. I tried addressing by interface name and MAC address and neither works.

Contributor guide

Open the contributing guide

Research direction

Reproduce the failure with the vmware-k8s-1.24-v1.17.0 OVA and the net.toml on the 12th partition. Start with netdog's network configuration parser and the NetworkDeviceV1 error, comparing the supplied MAC-address and interface-name forms with the accepted configuration shape. Done means the static configuration parses and the VMware image boots with the requested address and route.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
networking, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.