Open ruudgrosmann opened 2 years ago
@thbar @sfgeorge what do you think about this one?
That's very helpful that this workaround is documented for people who hit this issue.
But I'm wary to build that in though for a few reasons, mainly because we will be blindly saying 'yes' to any other anticipating prompts that come up, from RVM, Ruby or otherwise.
Moreover, A fresh install of RVM & a Ruby should not trigger RVM to be prompting this. This is either a bug in RVM (which I am unsuccessful at reproducing) or the result of an environmental factor on the machine in question.
@ruudgrosmann So I can try again to reproduce this, would you be kind enough to provide this info?
/home/deploy/.rvm
./etc/rvmrc
/home/deploy/.rvmrc
@pkuczynski it is the type of temporary issues for which I usually create a fork myself, report the problem back upstream, until the upstream problem is fixed.
Completely agree with the points raised by @sfgeorge, and we can investigate though!
Let's wait if @ruudgrosmann will come up with reproducible case, otherwise we will close...
In the meantime I have upgraded my OS and as well ansible. I have tried reproducing this issue successfully though. On the install server, I removed ruby and tried reinstalling it. After the cpu load dropped, I could see from the output of rvm (on the install server) that the ruby was installed, but on the host ansible was still busy doing nothing.
The information you asked for:
hosts: bullseye
remote_user: deploy
vars:
the rvm.ruby install: tarfile created, but I cannot attach it here. I have no graphical file manager to drag and drop or copy it to the clip board. Can I upload it somewhere?
Maybe use https://wetransfer.com?
Thank you, @ruudgrosmann! Investigating.
@ruudgrosmann, I haven't yet been able to successfully reproduce this. Could I trouble you for some additional context?
ls -lah /data | head -n 2
? Looking just for the permissions on the /data directory./data/rvm
?rvm list
, do you get the same Do you wish to trust . . . confirmation prompt?If you're curious, here's the branch where I'm attempting to replicate your setup as close as possible. And here are the test results, which are currently successful.
The output from the ansible install on the installation server is the same as in the question: the do-you-wish-to-trust message The value of the jrubybversion is not that relevant for the problem, because the problem occurs before the playbook tries to install jruby, but its value is jruby-9.2.14.0 The /data directory has owner root, group ruud and file mode 775. So user deploy is not allowed to write in it. If I log in on the install server as deploy, rvm list does not come with the confirmation request, but lists the rubies without problem.
The tarfile of /data/rvm on the installation server: https://wetransfer.com/downloads/33087c8b9958189f0499d89820ed4a3820220330080110/56682745348102f1f3a18a88d4533fb220220330080127/2a1921
By reading the rvm script _rvmrctrust I found another workaround for this problem, which does not include hacking the rvm.ruby role code. That would be to add a line to the deploy user's .rvmrc
rvm_trust_rvmrcs_flag=1
in a seperate role prior to running the rmv.ruby role. Not perfect either, but visible in the playbook.
I noticed that installing a ruby on a remote server with a user install always hangs after some time. The ruby appears to be installed, but the ansible-playbook command hangs. I figured out what is going on by adding a redirect to the install command and keeping an eye on the output file. The rvm command asks for user input and the ansible task hangs.
I see this in the rvm output:
Ideally, rvm should have an option to force install. I posted an issue on their github. I resolved this locally by editing rubies.yml in the rvm.ruby distribution and replacing
command: '{{ rvm1_rvm }} install {{ item.item }} {{ rvm1_ruby_install_flags }}'
byshell: "bash -c 'yes | {{ rvm1_rvm }} install {{ item.item }} {{ rvm1_ruby_install_flags }} '"
It is not a nice solution, but for now it works: ansible does not hang on the install rubies task.