summaryrefslogtreecommitdiff
path: root/cloudinit/config
diff options
context:
space:
mode:
authorScott Moser <smoser@ubuntu.com>2016-03-07 21:31:25 -0500
committerScott Moser <smoser@ubuntu.com>2016-03-07 21:31:25 -0500
commit6e31038b9cccbcb4a33693060b96fc4f71d86789 (patch)
tree56db6fa77cac88b32dd56b28300fe6e129b0f7e4 /cloudinit/config
parent5db46cfb68422b0c14d4a6c097553edd0016de3f (diff)
downloadvyos-cloud-init-6e31038b9cccbcb4a33693060b96fc4f71d86789.tar.gz
vyos-cloud-init-6e31038b9cccbcb4a33693060b96fc4f71d86789.zip
No longer run pollinate by default in seed_random
The user can still choose to run pollinate here to seed their random data. And in an environment with network datasource, that would be expected to work. However, we do not want to run it any more from cloud-init because a.) pollinate's own init system jobs should get it ran before ssh, which is the primary purpose of wanting cloud-init to run it. b.) with a local datasource, there is no network guarantee when init_modules run, so pollinate -q would often cause issues then. c.) cloud-init would run pollinate and log the failure causing many cloud-init specific failures that it could do nothing about. LP: #1554152
Diffstat (limited to 'cloudinit/config')
-rw-r--r--cloudinit/config/cc_seed_random.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/cloudinit/config/cc_seed_random.py b/cloudinit/config/cc_seed_random.py
index 3288a853..1b011216 100644
--- a/cloudinit/config/cc_seed_random.py
+++ b/cloudinit/config/cc_seed_random.py
@@ -83,7 +83,7 @@ def handle(name, cfg, cloud, log, _args):
len(seed_data), seed_path)
util.append_file(seed_path, seed_data)
- command = mycfg.get('command', ['pollinate', '-q'])
+ command = mycfg.get('command', None)
req = mycfg.get('command_required', False)
try:
env = os.environ.copy()