cloud-init

UrlError from #include aborts stage

Bug #1720844 reported by Andrew Jorgensen on 2017-10-02

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	cloud-init	Fix Released	Medium	Unassigned

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.