This issue was found while running acceptance tests for Uyuni:
FAIL: mgrctl cp server:/var/log/rhn/reposync.log /tmp/reposync.log returned status code = 1.
Output:
4:16PM INF Starting mgrctl cp server:/var/log/rhn/reposync.log /tmp/reposync.log
4:16PM INF Error: 1 error occurred:
* copying from container: copier: get: "/var/log/rhn/reposync.log": copying /var/log/rhn/reposync.log: archive/tar: write too long
It seems this error happens when the source file is being updated at the same time that mgrctl cp is preparing for transfering the file.
Maybe mgrctl cp could create a temporal copy of the source file and use it for the transfer, so we can prevent this situation.
This issue was found while running acceptance tests for Uyuni:
It seems this error happens when the source file is being updated at the same time that
mgrctl cpis preparing for transfering the file.Maybe
mgrctl cpcould create a temporal copy of the source file and use it for the transfer, so we can prevent this situation.