[16:38] <blackboxsw> Church: sorry for the response delay: `cloud-init status --wait --long` should tell you why cloud-init exited if it is exiting earlier than you expect. There are some error conditions or cloud-init being "disabled" that would trigger an early exit of the --wait un the expectation that cloud-init won't run anymore or won't run at all.
[16:40] <blackboxsw> holtgrewe: yes correct network config cannot be provided by cloud-init user-data because user-data is processed only after network is already up on a system (in case that user-data has to consume data/packages on the network)
[16:40] <blackboxsw> https://cloudinit.readthedocs.io/en/latest/topics/network-config.html#default-behavior "User-data cannot change an instance’s network configuration. In the absence of network configuration in any of the above sources , Cloud-init will write out a network configuration that will issue a DHCP request on a “first” network interface."
[16:42] <blackboxsw> so network config would need to be provided on-disk in /etc/cloud/cloud.cfg.d/some.cfg or via kernel cmdline or in Openstack's case via network_data.json config