[Bug 296638] Nuageinit network-config d oesn’t work with “network” key in yaml
[email protected] Thu, 09 Jul 2026 11:51:13 +0000
| Newsgroups | gmane.os.freebsd.bugs |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=296638
Bug ID: 296638
Summary: Nuageinit network-config doesn’t work with “network”
key in yaml
Product: Base System
Version: 14.4-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: bin
Assignee: [email protected]
Reporter: [email protected]
When using the following yaml with vm-bhyve’s “vm configure fbsd14-x64
network-config” using a FreeBSD 14.4 CI image
(FreeBSD-14.4-RELEASE-amd64-BASIC-CLOUDINIT-zfs.qcow2) nuageinit doesn’t set
the network (addresses changed to documentation ones)
network:
ethernets:
vtnet0:
dhcp4: false
dhcp6: false
addresses:
- 192.0.2.27/24
- 2001:db8:cafe:1::1b/64
gateway4: 192.0.2.1
gateway6: fe80::2e3a:fdff:feed:3571
nameservers:
addresses: [2001:db8:cafe:1::53, 2001:db8:f00d:1::53]
After some tinkering in lua it seems the configuration is read in another
internal data structure with key “network” dus rendering it a bit like
network:
network:
ethernets:
…
This seems to happen in the function parse_network_config()
(libexec/nuageinit/nuageinit) where a netobj["network"] = obj is done. That
probably needs to be a netobj["network"] = obj[“network”]. Of course it can
fall back to the old behaviour if the “network” key isn’t in obj.
The same config doesn’t as advertised (with different interface names of
course) with a Linux cloud-init bootstrapped VM
--
You are receiving this mail because:
You are the assignee for the bug.