[03:54] <blackboxsw> toolsmith: if you get a chance to file a bug @  https://bugs.launchpad.net/cloud-init/+filebug requesting "jinja-template doesn't support 'do' extension. I bet we can fix it pretty easily it looks like all we'd need is to load the jinja2.ext.do extension during our template rendering. Then you wouldn't have to workaround a lack of that extension in cloud-init jinja handling.
[03:54] <blackboxsw> Testing on my end I got do commands to work with only this diff https://paste.ubuntu.com/p/5KY4PGd6kg/
[03:56] <blackboxsw> we'd only need a minor add to unittests tests/unittests/test_templating.py to exercise that case.
[03:58] <blackboxsw> https://paste.opendev.org/show/bBfoMnqjJr4BNP8jL4zi/ if you don't have Ubuntu SSO login :
[03:58] <toolsmith> blackboxsw that's great. I'll open a bug tomorrow morning EST. Thanks again.
[03:59] <blackboxsw> rock! I'll either put up a branch or can help shepherd a pull request from you into cloud-init upstream if you were so inclined.
[06:50] <jonx> Hello. I'm currently experiencing an issue where VMs I launch it vsphere with a static IP configuration is falling back to DHCP before cloud init completes its build. Has anyone experienced this issue before?