summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorScott Moser <smoser@ubuntu.com>2012-02-17 13:19:26 -0500
committerScott Moser <smoser@ubuntu.com>2012-02-17 13:19:26 -0500
commit9c37781563e79e1c816632725a3890ea0955a5f6 (patch)
tree2284c8cfebc3fee893d9c0087e51d4d88cf4a302
parent02aea2383e0ea020fd6c2e74ffcaad8983820a9d (diff)
downloadvyos-cloud-init-9c37781563e79e1c816632725a3890ea0955a5f6.tar.gz
vyos-cloud-init-9c37781563e79e1c816632725a3890ea0955a5f6.zip
cloud-init.py: exit success if no data sources found
previously, cloud-init would exit failure if no data sources were found. In the case of cloud-init-local, that was often the case. In the case of cloud-init (net) it is a bit more likely that the user would consider it failure if nothing was found. Potentially this could even be user-configurable.
-rwxr-xr-xcloud-init.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/cloud-init.py b/cloud-init.py
index 9d559020..9e0a0405 100755
--- a/cloud-init.py
+++ b/cloud-init.py
@@ -136,7 +136,7 @@ def main():
cloud.get_data_source()
except cloudinit.DataSourceNotFoundException as e:
sys.stderr.write("no instance data found in %s\n" % cmd)
- sys.exit(1)
+ sys.exit(0)
# set this as the current instance
cloud.set_cur_instance()