Actions
Bug #32814
closedAnsible crashes if working_dir does not exist
Difficulty:
Triaged:
No
Description
2021-06-15T16:50:29 4bbccf26 [E] <Errno::ENOENT> No such file or directory @ dir_s_mkdir - /home/aruzicka/.foreman-ansible/d20210615-74610-jrg7o6 $HOME/.rvm/rubies/ruby-2.7.0/lib/ruby/2.7.0/tmpdir.rb:85:in `mkdir' $HOME/.rvm/rubies/ruby-2.7.0/lib/ruby/2.7.0/tmpdir.rb:85:in `block in mktmpdir' $HOME/.rvm/rubies/ruby-2.7.0/lib/ruby/2.7.0/tmpdir.rb:129:in `create' $HOME/.rvm/rubies/ruby-2.7.0/lib/ruby/2.7.0/tmpdir.rb:83:in `mktmpdir' smart-proxy-ansible/lib/smart_proxy_ansible/runner/ansible_runner.rb:190:in `working_dir' smart-proxy-ansible/lib/smart_proxy_ansible/runner/ansible_runner.rb:16:in `initialize' smart-proxy-dynflow/lib/smart_proxy_dynflow/action/batch_runner.rb:11:in `new' smart-proxy-dynflow/lib/smart_proxy_dynflow/action/batch_runner.rb:11:in `initiate_runner' smart-proxy-dynflow/lib/smart_proxy_dynflow/action/runner.rb:40:in `init_run' smart-proxy-dynflow/lib/smart_proxy_dynflow/action/runner.rb:10:in `run'
Updated by The Foreman Bot over 3 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/smart_proxy_ansible/pull/50 added
Updated by Ondřej Pražák over 3 years ago
Still reproducible with:
:working_dir: '/tmp/bar/baz/boo'
Updated by Adi Abramovitch over 3 years ago
- Pull request deleted (
https://github.com/theforeman/smart_proxy_ansible/pull/50)
Updated by The Foreman Bot over 3 years ago
- Pull request https://github.com/theforeman/smart_proxy_ansible/pull/52 added
Updated by Ondřej Ezr over 3 years ago
I don't think we want to fix this.
Would a validation of that setting (if the dir in setting doesn't exist fail to init the proxy) be a proper fix?
Or should we try to create the working directory?
Updated by The Foreman Bot over 3 years ago
- Pull request https://github.com/theforeman/smart_proxy_ansible/pull/53 added
Updated by The Foreman Bot over 3 years ago
- Fixed in Releases smart_proxy_ansible-3.3.0 added
Updated by Adi Abramovitch over 3 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset smart_proxy_ansible|70af2956015e298e203499ff218a6945c9fb1e0d.
Actions