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 OpenStack. We can't reasonably support all possible data or data formats you produce on a disk and label it 'config-2'. You point out that the fix seems straight forward enough, but if we modify cloud-init to handle you're slightly-modified ConfigDrive then how can we test and make sure that this doesn't regress in the future? If you'd like us to look at this bug further, please run 'cloud-init collect-logs' and attach the cloud-init.tar.gz file that it creates. Also, please give more information on how you've modified your openstack. I've poked a bit and I can create a failing unit test, and a change to make that test not fail: http://paste.ubuntu.com/p/YRPXTPm5hj/ . The problem with this solution is that it will still render network configuration and have side effects. What you really need to do is properly tell cloud-init that network configuration is disabled. Currently the only way to do that is to place content in /etc/cloud.cfg.d/ that says 'network: config: disabled'. I'm sorry if I've misunderstood the bug, and you are actually not "hacking" an openstack to produce this. After you've provided the requested information, please set the bug status back to 'New' ** Changed in: cloud-init (Ubuntu) Status: Confirmed => Incomplete -- 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 fails if no network config is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1686338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
