Activity log for bug #1798117

Date Who What changed Old value New value Message
2018-10-16 14:43:23 Scott Moser bug added bug
2018-10-16 14:43:32 Scott Moser bug task added cloud-init
2018-10-16 14:43:38 Scott Moser cloud-init: status New Confirmed
2018-10-16 14:43:41 Scott Moser cloud-init (Ubuntu): status New Confirmed
2018-10-16 14:43:44 Scott Moser cloud-init: importance Undecided Medium
2018-10-16 14:43:46 Scott Moser cloud-init (Ubuntu): importance Undecided Medium
2018-10-16 14:43:54 Scott Moser bug task added juju
2018-10-16 16:25:59 Launchpad Janitor merge proposal linked https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/356850
2018-10-18 16:04:15 Richard Harding juju: status New Triaged
2018-10-18 16:04:18 Richard Harding juju: milestone 2.5-beta1
2018-10-18 16:04:21 Richard Harding juju: importance Undecided High
2018-11-09 15:29:43 Richard Harding juju: milestone 2.5-beta1 2.5-beta2
2018-11-22 08:31:02 Joseph Phillips juju: assignee Joseph Phillips (manadart)
2018-11-22 08:31:07 Joseph Phillips juju: status Triaged In Progress
2018-11-23 05:43:03 Joseph Phillips juju: status In Progress Fix Committed
2018-11-30 01:37:21 Ian Booth juju: milestone 2.5-beta2 2.5-beta3
2018-12-03 22:06:53 Server Team CI bot cloud-init: status Confirmed Fix Committed
2018-12-13 20:22:15 Ryan Harper cloud-init: status Fix Committed Fix Released
2018-12-15 05:07:16 Launchpad Janitor cloud-init (Ubuntu): status Confirmed Fix Released
2019-03-22 01:40:50 Anastasia juju: status Fix Committed Fix Released
2020-12-08 14:49:40 Scott Moser description == Short summary == In lxd containers launched by juju, /var/lib/cloud/seed/nocloud-net/network-config has: has: network: config: disabled That is invalid content. Cloud-init assumes content in 'network-config' is already namespaced to 'network'. The correct content would be: config: disabled == Easy recreate == $ lxc launch ubuntu-daily:bionic \ "--config=user.network-config={'network': {'config': {'disabled'}}}" == Longer Info == When looking at bug 1651497, I see containers that run cloud-init have errors in a container's cloud-init log (http://paste.ubuntu.com/p/5mKXC8pMwH/) like: AttributeError: 'NoneType' object has no attribute 'iter_interfaces' and Failed to rename devices: Failed to apply network config names. Found bad network config version: None After some looking guessing I realized that juju must be attempting to disable cloud-init's network configuration via sending the following into the nocloud seed (/var/lib/cloud/seed/nocloud-net/network-config) via 'user.network-config'. cloud-init can clearly handle this better, but juju should not be sending invalid configuration. Related bugs: * bug 1651497: iscsid.service fails to start in container, results in failed dist-upgrade later on ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cloud-init 18.3-9-g2e62cb8a-0ubuntu1~18.04.2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CloudName: NoCloud Date: Tue Oct 16 14:33:12 2018 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) cloud-init-log-warnings: 2018-10-16 14:32:01,706 - stages.py[WARNING]: Failed to rename devices: Failed to apply network config names. Found bad network config version: None 2018-10-16 14:32:01,707 - util.py[WARNING]: failed stage init-local AttributeError: 'NoneType' object has no attribute 'version' 2018-10-16 14:32:02,366 - stages.py[WARNING]: Failed to rename devices: Failed to apply network config names. Found bad network config version: None user_data.txt: #cloud-config {} == Short summary == In lxd containers launched by juju, /var/lib/cloud/seed/nocloud-net/network-config has:  has:  network:    config: disabled That is invalid content. Cloud-init assumes content in 'network-config' is already namespaced to 'network'. The correct content would be:   config: disabled == Easy recreate == $ lxc launch ubuntu-daily:bionic \    "--config=user.network-config={'network': {'config': {'disabled'}}}" == Longer Info == When looking at bug 1651497, I see containers that run cloud-init have errors in a container's cloud-init log (http://paste.ubuntu.com/p/5mKXC8pMwH/) like:   AttributeError: 'NoneType' object has no attribute 'iter_interfaces' and   Failed to rename devices: Failed to apply network config names. Found bad network config version: None After some looking guessing I realized that juju must be attempting to disable cloud-init's network configuration via sending the following into the nocloud seed (/var/lib/cloud/seed/nocloud-net/network-config) via 'user.network-config'. cloud-init can clearly handle this better, but juju should not be sending invalid configuration. Related bugs:  * bug 1651497: iscsid.service fails to start in container, results in failed dist-upgrade later on * bug 1906187: Version tag is not respected when put last ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cloud-init 18.3-9-g2e62cb8a-0ubuntu1~18.04.2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CloudName: NoCloud Date: Tue Oct 16 14:33:12 2018 PackageArchitecture: all ProcEnviron:  TERM=xterm-256color  PATH=(custom, no user)  LANG=C.UTF-8 SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) cloud-init-log-warnings:  2018-10-16 14:32:01,706 - stages.py[WARNING]: Failed to rename devices: Failed to apply network config names. Found bad network config version: None  2018-10-16 14:32:01,707 - util.py[WARNING]: failed stage init-local  AttributeError: 'NoneType' object has no attribute 'version'  2018-10-16 14:32:02,366 - stages.py[WARNING]: Failed to rename devices: Failed to apply network config names. Found bad network config version: None user_data.txt:  #cloud-config  {}
2023-05-11 16:02:30 James Falcon bug watch added https://github.com/canonical/cloud-init/issues/3251