Comment 5 for bug 1303925

cloud-init is executing code that maas told it to execute.
so maas needs to tell it to execute code that has some "last ditch catch".

to be clear, cloud-init got data from maas (via kernel cmdline) that told it to tell get some code from the metadata server to execute. It then executed it. That code failed. *that* is the code that needs to be more resilient. cloud-init is, by design, very much doing exactly what maas tells it to do.