default not accepted as destination in routes: in the network-config
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
High
|
Alberto Contreras |
Bug Description
I have this network-config file (which is valid as per netplan
version: 2
ethernets:
enp0s3:
dhcp4: false
addresses: [10.0.4.10/24]
nameservers:
addresses: [10.0.4.1]
routes:
- to: default
via: 10.0.4.1
metric: 100
And cloud-config bumps on the 'default':
022-06-14 10:30:10,662 - util.py[WARNING]: failed stage init-local
failed run of stage init-local
-------
Traceback (most recent call last):
File "/usr/lib/
ret = functor(name, args)
File "/usr/lib/
...
File "/usr/lib/
, in _normalize_net_keys
raise ValueError(
ValueError: Address default is not a valid ip address
-------
student@osm11:~$ uname -a
Linux osm11 5.4.0-117-generic #132-Ubuntu SMP Thu Jun 2 00:39:06 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
student@osm11:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_
DISTRIB_
DISTRIB_
With the cloud-enabled OVA from
https:/
Changed in cloud-init: | |
assignee: | nobody → Alberto Contreras (aciba) |
status: | Triaged → In Progress |
Changed in cloud-init: | |
status: | Fix Committed → Fix Released |
status: | Fix Released → Fix Committed |
Changed in cloud-init: | |
status: | Fix Committed → Fix Released |
Hey Pedro, it appears as though the netplan renderer isn't getting selected as it should be, but I need to see the logs to know for sure. Please run 'cloud-init collect-logs' and attach the resulting tarball to this ticket, then you can set the status back to 'New'.