Problems setting up a trove
by Baumann, Christoph (C.)
Hello,
currently I'm struggling with setting up a trove.
The building in Baserock (16.13) and also deploying it to VirtualBox worked.
After some struggle with the correct network settings I was able to log in and noticed that systemd failed to bring up trove-setup:
"
Apr 28 11:55:24 durlach-trove ansible-playbook[331]: fatal: [localhost] => Authentication or permission failure. In some cases, you may have been able to authenticate and did not have permissions on the remote directory. Consider changing the remote temp path in ansible.cfg to a path rooted in "/tmp". Failed command was: mkdir -p $HOME/.ansible/tmp/ansible-tmp-1461844524.24-189921729673453 && echo $HOME/.ansible/tmp/ansible-tmp-1461844524.24-189921729673453, exited with result 127
Apr 28 11:55:24 durlach-trove ansible-playbook[331]: TASK: [trove-setup | fail msg='TROVE_ID is mandatory'] ************************
Apr 28 11:55:24 durlach-trove ansible-playbook[331]: skipping: [localhost]
Apr 28 11:55:24 durlach-trove ansible-playbook[331]: FATAL: all hosts have already failed -- aborting
Apr 28 11:55:24 durlach-trove ansible-playbook[331]: PLAY RECAP ********************************************************************
Apr 28 11:55:24 durlach-trove ansible-playbook[331]: localhost : ok=0 changed=0 unreachable=1 failed=0
"
After calling trove-setup in the login shell (root) the setup started and after a while reported success. Then the mirroring of the upstream trove that was configured in the build process started.
Also the web interface came up. But there seems to be an issue with git. The web interface reports "Repository seems to be empty" for any repository I click on. And also 'git clone' fails with a similar error.
But: if I use the ssh ID of the lorry user the checkout succeeds. This also works to checkout the trove-config. But it fails to push changes.
Further the git user has /bin/bash as login shell and no commands for git-shell are available.
Could it be that running trove-setup from an interactive root-shell broke the setup?
Regards,
Christoph