meta-data not always correctly set

[adamretter]

When specifying a cloud-init meta-data file to uvt-kvm using:
--meta-data /tmp/22720db9-abaf-4ab4-a602-fe16e76715bd-meta-data

Where the content of the /tmp/22720db9-abaf-4ab4-a602-fe16e76715bd-meta-data file is:

instance-id: 22720db9-abaf-4ab4-a602-fe16e76715bd
local-hostname: my-vm-123
network-interfaces: |
  iface ens3 inet static
  hwaddress ether 06:00:00:42:9b:44
  address 54.36.67.139
  network 54.36.67.139
  netmask 255.255.255.255
  broadcast 5.196.205.132
  gateway 91.121.89.254
  dns-nameservers 213.186.33.99
  dns-search mydomain.com

Once the VM is booted, I find that not all of the meta-data settings have taken effect, but some have!
1) sudo ifconfig -a reports:

ens3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 54.36.67.139 netmask 255.255.255.255 broadcast 0.0.0.0
        inet6 fe80::ff:fe42:9b84 prefixlen 64 scopeid 0x20<link>
        ether 06:00:00:42:9b:44 txqueuelen 1000 (Ethernet)
        RX packets 8047 bytes 499794 (499.7 KB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 5 bytes 426 (426.0 B)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

From this we can see that the "broadcast" was not set, whilst the "address" and "netmask" were. Why is the broadcast not set?

2) sudo route reports:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface

So it seems also that the default gateway has not been set from the meta-data either.

I am rather confused as to why some things are set and others are not, I have checked the cloud-init docs and it seems to me that I have the syntax of the meta-data file correct.

Can someone help with this please? I am wondering if this is a bug?

[Robie Basak (racb)]

Thank you for the report.

Inside the VM, please could you check the metadata that was actually supplied to cloud-init? For example, the output of:

$ sudo mount -o ro /dev/vdb /mnt
$ cat /mnt/meta-data

If uvtool passed meta-data as expected and that file is identical to what you specified, then this would best be followed up with cloud-init upstream, as that would confirm that the behaviour you're seeing is entirely down to cloud-init and not uvtool.

[Launchpad Janitor (janitor)]

[Expired for uvtool because there has been no activity for 60 days.]