Open queglay opened 4 years ago
Files identified in the description:
If these files are incorrect, please update the component name
section of the description or use the !component
bot command.
I've used fetch a lot in my AWS infrastructure, and I just saw another occurance with this related to another log file. I suspect that since those logs are being updated at the time of the fetch, the checksum changes between the check time and the copy operation.
If the theory is correct, fetch could perhaps copy the file to another location first, then perform the copy and checksum from this copied file, which shouldn't change any further.
So if this is a race condition for files that are being updated during the fetch operation, I do not think we should copy it by default (file might still require more data to be written). But an option to force the fetch anyways might be a solution to your issue. (--ignore-checksum-changes? .. bikeshed away).
Files identified in the description:
If these files are incorrect, please update the component name
section of the description or use the !component
bot command.
I figured a file copy first and checksum on the copy would be better than no checksum at all.
SUMMARY
Fetch results in checksum mismatch. Become must be used to acquire it from the location due to permissions.
ISSUE TYPE
COMPONENT NAME
fetch
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
ubuntu 16.04
STEPS TO REPRODUCE
EXPECTED RESULTS
It should fetch the file without any error.
ACTUAL RESULTS