There might be a microsec difference. We probably need to sync fs after writing the file before we attempt to launch it.
: 2018-02-06T15:01:51Z : Calling: /var/lib/slipstream/module_apps_containers_rancher_16339__post-install
: 2018-02-06T15:01:51Z :
ERROR: Failing... Failed running 'module/apps/Containers/Rancher/16339:Post-install' script on 'machine': [Errno 2] No such file or directory
Traceback (most recent call last):
File "/opt/slipstream/client/lib/slipstream/executors/MachineExecutor.py", line 278, in _launch_script
rc, stderr_last_line = self._run_target_script(script, exports, ignore_abort=ignore_abort, name=name)
File "/opt/slipstream/client/lib/slipstream/executors/MachineExecutor.py", line 307, in _run_target_script
process = self._launch_process(target_script, exports, name)
File "/opt/slipstream/client/lib/slipstream/executors/MachineExecutor.py", line 398, in _launch_process
process = util.execute(fn, noWait=True, extra_env=exports, withStderr=True)
File "/opt/slipstream/client/lib/slipstream/util.py", line 259, in execute
process = subprocess.Popen(commandAndArgsList, **kwargs)
File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
There might be a microsec difference. We probably need to sync fs after writing the file before we attempt to launch it.