Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Playbooks location compatibility for < v5.1 #987

Closed
gavindsouza opened this issue May 7, 2020 · 0 comments · Fixed by #988
Closed

Playbooks location compatibility for < v5.1 #987

gavindsouza opened this issue May 7, 2020 · 0 comments · Fixed by #988

Comments

@gavindsouza
Copy link
Collaborator

I get this error now:

Logs are saved under /tmp/logs/easy-install__2020-05-07__07-43.log
Checking System Compatibility...
ubuntu 18 is compatible!
curl already installed!
wget already installed!
git already installed!
pip3 already installed!
Traceback (most recent call last):
  File "install.py", line 437, in <module>
    install_bench(args)
  File "install.py", line 211, in install_bench
    run_playbook('create_user.yml', extra_vars=extra_vars)
  File "install.py", line 362, in run_playbook
    success = subprocess.check_call(args, cwd=os.path.join(cwd, 'bench', 'playbooks'), stdout=log_stream, stderr=sys.stderr)
  File "/usr/lib/python3.6/subprocess.py", line 306, in check_call
    retcode = call(*popenargs, **kwargs)
  File "/usr/lib/python3.6/subprocess.py", line 287, in call
    with Popen(*popenargs, **kwargs) as p:
  File "/usr/lib/python3.6/subprocess.py", line 729, in __init__
    restore_signals, start_new_session)
  File "/usr/lib/python3.6/subprocess.py", line 1364, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/.bench/bench/playbooks': '/tmp/.bench/bench/playbooks'

Here are the logs

Hit:1 http://at.archive.ubuntu.com/ubuntu bionic InRelease
Hit:2 http://at.archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:3 http://at.archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit:4 http://at.archive.ubuntu.com/ubuntu bionic-security InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
build-essential is already the newest version (12.4ubuntu1).
libffi-dev is already the newest version (3.2.1-8).
python3-setuptools is already the newest version (39.0.1-2).
git is already the newest version (1:2.17.1-1ubuntu0.7).
python3-dev is already the newest version (3.6.7-1~18.04).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Requirement already up-to-date: setuptools in /usr/local/lib/python3.6/dist-packages (46.1.3)
Requirement already up-to-date: cryptography in /usr/local/lib/python3.6/dist-packages (2.9.2)
Requirement already up-to-date: ansible==2.8.5 in /usr/local/lib/python3.6/dist-packages (2.8.5)
Requirement already up-to-date: pip in /usr/local/lib/python3.6/dist-packages (20.1)
Requirement already satisfied, skipping upgrade: six>=1.4.1 in /usr/local/lib/python3.6/dist-packages (from cryptography) (1.14.0)
Requirement already satisfied, skipping upgrade: cffi!=1.11.3,>=1.8 in /usr/local/lib/python3.6/dist-packages (from cryptography) (1.14.0)
Requirement already satisfied, skipping upgrade: jinja2 in /usr/local/lib/python3.6/dist-packages (from ansible==2.8.5) (2.11.2)
Requirement already satisfied, skipping upgrade: PyYAML in /usr/local/lib/python3.6/dist-packages (from ansible==2.8.5) (5.3.1)
Requirement already satisfied, skipping upgrade: pycparser in /usr/local/lib/python3.6/dist-packages (from cffi!=1.11.3,>=1.8->cryptography) (2.20)
Requirement already satisfied, skipping upgrade: MarkupSafe>=0.23 in /usr/local/lib/python3.6/dist-packages (from jinja2->ansible==2.8.5) (1.1.1)
Install script run at 07:43 on 2020-05-07

System is a freshly installed and updated Ubuntu 18.4 LTS.

Originally posted by @tobiasfeistmantl in #980 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant