yahoo-eng-team team mailing list archive

[James Falcon <1901701@xxxxxxxxxxxxxxxxxx>]

Default behavior in 18.04 was to create and use the fallback networking
config. That involved using DHCP to discover which interface to use.
Since you're disabling DHCP, I'm not surprised that the networking isn't
working for you. That behavior has changed in 20.04 to apply a
networking configuration as you're expecting, but we have specifically
disabled this behavior for releases prior to 20.04 as to not break
existing installations by changing the expected network config.

You can manually enable the networking config by following the directions here:
https://cloudinit.readthedocs.io/en/latest/topics/datasources/openstack.html#configuration
So for your case that would look like:
datasource:
  OpenStack:
    apply_network_config: True

I'm going to close this ticket because I believe cloud-init is working as expected. If 
you believe there is still a problem I haven't addressed, feel free to reopen it.

** Changed in: cloud-init
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1901701

Title:
  cloud-init is not able to configure IPv6 in Ubuntu 18.04

Status in cloud-init:
  Invalid

Bug description:
  I am trying to create a Ubuntu 18.04 VM using Openstack solution, I
  want to assign IPv6 to the VM and I have disabled DHCP in the IPv6
  subnet. It is noticed that cloud-init is able to read the network
  related information from the metadata url but not using it to assign
  it to the VM.

  I noticed that it is not updating the /etc/netplan/50-cloud-init.yaml
  file with proper configuration.

  Cloud-Init version being used is 20.2 "/usr/bin/cloud-init
  20.2-45-g5f7825e2-0ubuntu1~18.04.1".

  I am attaching the cloud-init logs for the reference.

  Below is the Rest API Output for network info
  root@test-ubuntu-18:~# curl http://169.254.169.254/openstack/latest/network_data.json
  {"services": [{"type": "dns", "address": "8.8.8.8"}, {"type": "dns", "address": "2001:4860:4860::8888"}], "networks": [{"network_id": "511****a166-7f3e-432e-bbf3-c006ccc4fb78", "link": "tap7422d0eb-8a", "type": "ipv4_dhcp", "id": "network0"}, {"network_id": "511****7f3e-432e-bbf3-c006ccc4fb78", "type": "ipv6", "services": [{"type": "dns", "address": "2001:4860:4860::8888"}], "netmask": "ffff:ffff:ffff:ffff::", "link": "tap7422d0eb-8a", "routes": [{"netmask": "::", "network": "::", "gateway": "2***:****:****:****::1"}], "ip_address": "2***:****:****:****::13f", "id": "network1"}], "links": [{"ethernet_mac_address": "fa:16:3e:16:09:37", "mtu": 1500, "type": "bridge", "id": "tap7422d0eb-8a", "vif_id": "7422d0eb-8aa5-4310-859c-8f60456045d9"}]}

  Things are working well with Ubuntu 20.04. I am not sure, what am I
  missing here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1901701/+subscriptions