Public bug reported: If you have a bad URL or inaccessible server referenced in an #include document, a cloudinit.url_helper.UrlError is thrown which is not caught, so it aborts the stage and an instance can be left unconfigured.
I've proposed a patch here: https://code.launchpad.net/~ajorgens/cloud- init/+git/cloud-init/+merge/331660 Obviously a bad URL is not a great case, but aborting and leaving the instance unconfigured seems the worst choice in this scenario because it may not even be possible to log in to troubleshoot. ** Affects: cloud-init Importance: Undecided Status: New -- 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/1720844 Title: UrlError from #include aborts stage Status in cloud-init: New Bug description: If you have a bad URL or inaccessible server referenced in an #include document, a cloudinit.url_helper.UrlError is thrown which is not caught, so it aborts the stage and an instance can be left unconfigured. I've proposed a patch here: https://code.launchpad.net/~ajorgens /cloud-init/+git/cloud-init/+merge/331660 Obviously a bad URL is not a great case, but aborting and leaving the instance unconfigured seems the worst choice in this scenario because it may not even be possible to log in to troubleshoot. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1720844/+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