-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After an upgrade fails to download, subsequent upgrades will fail #693
Comments
Here we go.
I think this will be one of your main signals (unexpected EOF):
Directory content at the time:
After I removed the 0 byte file, upgrading was successful. I haven't been able to find the actual download for this file in the logs. I created an extract which you can find on my G-drive, here. |
When there is an issue during the download of an artifact, it might happen that the agent does not manage to clean up the downloaded files. That results on 0 bytes files present, which makes the agent to understand the artifacts were successfully downloaded and then move on to the sha512 check. The check fails due to the fact the agent does not find the checksum on the .sha512 file. Below are the logs of this issue.
So far the issue seems to be on the clean up procedure that expects the file path to be returned, however on failure the download method does not returns it. |
@WiegerElastic, @joshdover there are 2 different errors here:
|
Hi @joshdover Observations:
As per attached PR #752 :
Could you please confirm if we are expecting this? Please let us know if we are missing anything here. |
@amolnater-qasource Was subsequent upgrade blocked with 0 file present in your 8.4.0 test? If yes, can we re-open this issue please? |
Hi @gbanasiak Build details: Please let us know if we are missing anything. |
We have reports that after an upgrade fails to download, subsequent upgrade attempts can fail with an error about a 0 byte file when trying to validate the sha and/or signature of the download.
More details needed cc @WiegerElastic
The text was updated successfully, but these errors were encountered: