Setting this to Incomplete for MAAS, since it's not clear from if bad input data from MAAS is causing this traceback in cloud-init, or if the bug is only in cloud-init.
@jamesbeedy, can you tell us about how you have configured/customized your apt sources in MAAS? ** Also affects: cloud-init Importance: Undecided Status: New ** Changed in: maas Status: New => Incomplete -- 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/1735950 Title: ValueError: Old and New apt format defined with unequal values True vs False @ apt_preserve_sources_list Status in cloud-init: New Status in MAAS: Incomplete Bug description: All nodes have these same failed events: Node post-installation failure - 'cloudinit' running modules for config Node post-installation failure - 'cloudinit' running config-apt- configure with frequency once-per-instance Experiencing odd issues with the squid proxy not being reachable. From a deployed node that had the event errors. $ sudo cat /var/log/cloud-init.log | http://paste.ubuntu.com/26098787/ $ sudo cat /var/log/cloud-init-output.log | http://paste.ubuntu.com/26098802/ ubuntu@os-util-00:~$ sudo apt install htop sudo: unable to resolve host os-util-00 Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: htop 0 upgraded, 1 newly installed, 0 to remove and 14 not upgraded. Need to get 76.4 kB of archives. After this operation, 215 kB of additional disk space will be used. Err:1 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 htop amd64 2.0.1-1ubuntu1 Could not connect to 10.10.0.110:8000 (10.10.0.110). - connect (113: No route to host) E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/universe/h/htop/htop_2.0.1-1ubuntu1_amd64.deb Could not connect to 10.10.0.110:8000 (10.10.0.110). - connect (113: No route to host) E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? Not sure if these things are related (the proxy not being reachable, and the node event errors) .... something is not right. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1735950/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp