Hi,
it would be nice to see the full /var/run/vmware-imc/cust.cfg that you are
using to configure it.
Just as an FYI - There are plenty of special-case network config sources
[1], I see that you fortunately use the generic one, but still on V1. If
you code up something new I'd recommend to switch to V2 [2].
Without the actual config from the file requested above I can only
derive from what I see in the log, so take it with a grain of salt. With
the config made available later that can be checked in detail.
version: 1
config:
type: physical,
name: ens160
mac_address: 00:50:56:bd:45:d2
subnets:
- control: auto,
type: dhcp
type: nameserver,
address:
- 10.117.21.1
- 10.117.21.2
search:
- dns.test.com
}
For now I can't see an obvious flaw, it even sort of matches an example in [3].
The config file requested will help, also I'll help raising it with the
cloud-init people.
[1]:
http://cloudinit.readthedocs.io/en/latest/topics/network-config.html#network-configuration-sources
[2]:
http://cloudinit.readthedocs.io/en/latest/topics/network-config-format-v2.html
[3]:
http://cloudinit.readthedocs.io/en/latest/topics/network-config-format-v1.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776452
Title:
Fail to set DNS server and search domain when customize Ubuntu18.04 to
DHCP IP by cloud-init
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1776452/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
