error 06-Oct-2020 19:51:13 Warning: Identity file /home/bamboo-agent/.ssh/id_rsa not accessible: No such file or directory. build 06-Oct-2020 19:51:14 sending incremental file list error 06-Oct-2020 19:51:14 rsync: failed to set permissions on "/home/frs/project/o/op/openmrs/.": Invalid argument (22)
@cintiadr did we make any changes that led to the above error?
I changed the rsync command within openmrs-contrib-bamboo and I see the same problem exists in the nightlybuild.sh script within puppet settings for the bamboo agents. But, I think Iâm over my head.
Should I have left the username as âopenmrsdev,openmrsâ? I havenât seen that syntax before and only the âopenmrsâ username works for me when I try accessing sourceforge with the key. How was this ever working? I changed the username to âopenmrsâ here, but not sure if that is necessary/correct. I also havenât run puppet before and I"m not seeing how openmrs-contrib-bamboo scripts are wired into the bamboo agents (havenât found a reference to that repo under the puppet folder).
So, I think:
$HOME/.ssh/id_rsa should be changed to $HOME/.ssh/sourceforge/id_rsa in this line
The username needs to be changed back to âopenmrsdev,openmrsâ in the line I changed or the username in nightlybuild.sh should be changed to âopenmrsâ
These changes need to somehow get deployed to our bamboo agents.
Iâm not quite sure what should happen with #1 & #2 and I donât know how to do #3 with puppet.
Thanks @cintiadr. I ran the ansible playbook for the 3 Bamboo agents. Hopefully that will help. Iâm still not 100% confident, since the nightlybuild.sh script seemed to have the exact same problem (rsync pointing to .ssh/ instead of .ssh/sourceforge/ and using âopenmrs,openmrsdevâ as a username for ssh), yet I donât see any recently missing nightly build artifacts on sourceforge.
BTW⊠it looks like limiting to multiple servers in my ansible-playbook command above leads to a race condition for the sshd role trying to remove entries locally from known_hosts, causing failed steps on 2 of 3 servers. Running the playbook for one server at a time was more reliable.
Of interest is this line: rsync: failed to set permissions on "/home/frs/project/o/op/openmrs/.": Invalid argument (22)
FWIW, despite these failures, the war file and readme have all along being uploaded to sourceforge. But because of these failures, the third release stage does not run and hence the standalone does not get uploaded to sourceforge.
Hello @dkayiwa@burke@cintiadr .Have also encountered similar issue trying to release refApp 2.11 with similar log however i was able to release referenceapp distro as seen here am only facing releasing to sourceforge as seen here