OK, I found the problem. I had tried to compile an up to date ruby from source which I thought I had removed, but in fact had not and this was the 2.5 release that I was executing, so the zlib issue was entirely due to the fact hat I had not compiled zlib in to that software.
I removed it, re-ran the RVM install, installed v2.5 and confirmed that it’s working. I then added “rvm use 2.5” to root’s profile as otherwise it insists on using the default ruby.
So I now have root using the correct ruby, but it’s missing the ‘bundler’ script/software/whatever-it-is. A little research gets me “gem install bundler”, so I have that command.
Now, if I run the /usr/share/one/install_gems script as root it says:
Don't run Bundler as root. Bundler can ask for sudo if it is needed, and
installing your bundle as root will break this application for all non-root
users on this machine.
although it does install the files. If I run is as my own UID it tells me I have to run the script as root…
Well, I let it run to completion and it looks like it installed OK, but sadly Sunstone fails to start.
I set the oneadmin user so that it is using the correct ruby by adding “rvm use 2.5” to the end of its .bash_profile but it fails to start. Running “systemctl start opennebula-sunstone” fails with the following errors in the messages file:
Mar 5 16:07:49 vmhost abrt: detected unhandled Ruby exception in '/usr/lib/one/sunstone/sunstone-server.rb'
Mar 5 16:07:49 vmhost abrt-server: Package 'opennebula-sunstone' isn't signed with proper key
Mar 5 16:07:49 vmhost ruby: from /usr/lib/one/sunstone/sunstone-server.rb:88:in `<main>'
Mar 5 16:07:49 vmhost systemd: opennebula-sunstone.service: main process exited, code=exited, status=1/FAILURE
Mar 5 16:07:49 vmhost systemd: Unit opennebula-sunstone.service entered failed state.
Mar 5 16:07:49 vmhost systemd: opennebula-sunstone.service failed.
I don’t know what the issue is and I’m rather poking around in the dark with RVM. It looks like it’s installed OK though, at least I get the right version number:
# ruby -v
ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-linux]
Any further thoughts?