@Prakash,
>From your logs it appears that you are booting under kvm and are using
the Ec2 Datasource. The metadata in that datasource is invalid. It
describes network information (as seen in /var/log/cloud-init.log and
cleaner in /run/cloud-init/instance-data.json) like this:
"network": {
"interfaces": {
"macs": {
"02:83:f8:24:b0:9c": {
"device-number": "0",
"interface-id": "eni-0ffc51e0fbd371979",
"local-hostname": "ip-10-110-227-52.delphix.com",
"local-ipv4s": "10.110.227.52",
That describes a nic with a nic with a MAC address of 02:83:f8:24:b0:9c.
but your system is booted with one like: 52:54:00:12:34:56
So in that sense, very much "Garbage in, Garbage out."
Now... that said, cloud-init is rendering network configuration in the
"network" stage, which I think is kind of buggy or at least requires
more thinking. I didn't think we were doing that. So we will look into
that a bit more, but I'm not sure the fix will fix your specific
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686338
Title:
cloud-init fails if no network config is set
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1686338/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
