Cloud-init also introduced a fix for
https://bugs.launchpad.net/bugs/1798117 which allows cloud-init to
handle popping off a top-level network key as provided by LXC, so either
approach will now work user.network-config vs user.user-data.
Thanks for this background Simos.
cloud-init 18.4 will
I made a change in the cloud-init configuration:
--- version1.profile2018-07-24 20:32:06.054307582 +0300
+++ version1.profile.after 2018-07-24 20:32:32.890558707 +0300
@@ -1,5 +1,5 @@
config:
- user.network-config: |
+ user.user-data: |
network:
version: 1
The following relate to LXD and the LXD container images for 16.04 and
18.04. Both container images have cloud-init 18.2 (18.2-4-g05926e48).
SUMMARY
cloud-init fails to set up networking if a container is launched with
cloud-init networking instructions.
WHAT WAS TESTED
16.04 container image
@Prakesh or others.
Based on last comment #12, I have set this to 'Incomplete'.
Please provide some more information and set the bug back to "New" when you're
done.
Thanks.
Scott
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
@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": {
Attached is the cloud init logs generated by "cloud-init collect-logs".
I can provide the QCOW2 image I used too, if it's useful, although it's
over 700M in size.
** Attachment added: "cloud-init collect-logs"
Sorry, I didn't mean to post that yet. The QCOW2 image we're using is
based on Ubuntu 18.04, and I can give any details about how we're
generating it, and/or it's contents (ubuntu-minimal plus some minor
configuration changes).
I can gather the logs requested from "cloud-init collect-logs" if
Hi Scott,
The error Serapheim described above was hit when running under QEMU;
e.g. with the following command:
$ sudo qemu-system-x86_64 -nographic -m 1G -drive file=ubuntu.qcow2
We're definitely not using OpenStack. The QCOW
--
You received this bug notification because you are a member
Hi,
I believe you're suggesting that cloud-init fails handle config-drive
data that you've provided it. From what I can understand, this config-
drive data is from a locally modified OpenStack.
Cloud-init does not support all possible things that look remotely like
a Config Drive from
Hit this again in 18.04:
```
[ 71.626777] cloud-init[1112]:
[ 71.636680] cloud-init[1112]: Traceback (most recent call last):
[ 71.641365] cloud-init[1112]: File
"/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line
Is there a difference between the network_data.json that is in
'/latest/' and the version that cloud-init reads?
It looks like we're not correctly handling the case where
network_data.json is present but contains '{}' Which I guess is a
bug, but I agree with Ryan in that i'm interested in
To follow up with the requested information, we are seeing this issue
with ConfigDrive and the 0.7.9-113-g513e99e0-0ubuntu1~16.04.1 version of
cloud-init. The contents of network_data.json are:
root@node1:/mnt/openstack/latest# cat network_data.json
{}
I'll proceed with disabling network
Hi Ryan
In our use-case, we use our own custom tool to configure the networking.
This tool reads a json file in /latest/ on the configdrive mount to get
its network config info. As such, we don't use cloud-init to configure
networking, and therefore network_data.json contains "{}". Should this
be
Agreed with your analysis in the description.
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Confirmed
--
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
Which datasource and what's included?
If no config is provided a fallback configuration is generated, but this
appears to suggest that a config was provided (but was empty)?
That's certainly a bug; I'd like to fully understand what's going on
though such that the datasource is returning an
Hi, Bernd Stolle --
A patch is certainly welcome, the code is here:
https://code.launchpad.net/cloud-init
Once you clone and fix, you can push up a branch to your repository on
launchpad. Once you do that, you can open a "merge proposal" by viewing
the branch in the LP UI, choosing'master' as
16 matches
Mail list logo
