You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 18, 2024. It is now read-only.
Some version changes are incompatible with old bootstrap attempts.
I can think of a couple ways to handle this, but I just wanted to lodge it as a concern.
Here's an example, this is the error from an old bootstrap and a new attempt to call python (but it's installed to a different location).
fatal: [10.10.10.10]: FAILED! => {"changed": false, "failed": true, "module_stderr": "Shared connection to 10.10.10.10 closed.\r\n", "module_stdout": "/home/core/pypy/bin/pypy: /lib64/libssl.so.1.0.0: no version information available (required by /home/core/pypy/bin/pypy)\r\n/home/core/pypy/bin/pypy: /lib64/libcrypto.so.1.0.0: no version information available (required by /home/core/pypy/bin/pypy)\r\nTraceback (most recent call last):\r\n File \"app_main.py\", line 75, in run_toplevel\r\n File \"/home/core/.ansible/tmp/ansible-tmp-1479847680.99-162471543187092/pip.py\", line 130, in <module>\r\n exitcode = invoke_module(module, zipped_mod, ANSIBALLZ_PARAMS)\r\n File \"/home/core/.ansible/tmp/ansible-tmp-1479847680.99-162471543187092/pip.py\", line 37, in invoke_module\r\n p = subprocess.Popen(['PATH=/home/core/bin:$PATH', 'python', module], env=os.environ, shell=False, stdout=subprocess.PIPE, stderr=subprocess.PIPE, stdin=subprocess.PIPE)\r\n File \"/home/core/pypy/lib-python/2.7/subprocess.py\", line 710, in __init__\r\n errread, errwrite)\r\n File \"/home/core/pypy/lib-python/2.7/subprocess.py\", line 1331, in _execute_child\r\n raise child_exception\r\nOSError: [Errno 2] No such file or directory\r\n", "msg": "MODULE FAILURE"}
The text was updated successfully, but these errors were encountered:
Some version changes are incompatible with old bootstrap attempts.
I can think of a couple ways to handle this, but I just wanted to lodge it as a concern.
Here's an example, this is the error from an old bootstrap and a new attempt to call python (but it's installed to a different location).
The text was updated successfully, but these errors were encountered: