-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Unable to update from 2019-08-14 to 2019-08-21 #8174
Comments
You can't do rolling upgrades from 14 to 21 as there is breakage of internode APIs all servers have to be updated together |
OK, well bosh updates all the servers one by one and after all 4 are updated none of them work. What should be the correct steps when doing an upgrade with Bosh? |
I did get the same issues upgrading two groups of servers from 2019-07-05T21-20-21Z to 2019-08-29T00-25-01Z. Services where stopped during the upgrade. One has some files with bitrot verification mismatch, one doesn't start at all (since he has issues on the configuration file, .minio.sys/config/config.json I noticed the issue using tcpdump, trying to debugg why my server wasen't starting at all. What is strange, is that it seems to use the wrong hash when trying to get the server. Exemple: On server3: hash==de5a64e690faa2d7f4afe22c6c5f2817d4987c81a29f1af7df66e94913a98c18 Server13 ask server3 with readall, he get a reply with hash==de5a64e690faa2d7f4afe22c6c5f2817d4987c81a29f1af7df66e94913a98c18 (witch is fine) Then he ask again with readfile and the hash in url, but put the hash of server 5 in the query (and get a bitrot verification mismatch) Here is the "raw" tcp requests with secrets removed:
Here are the content of the xl.json for my config.json file for each server: minio2: minio4: minio6: minio5: minio11: minio3: minio9: minio10: minio13: minio7: minio8: minio17: |
This is an issue is not related to bit-rot, it is related to how it is reading older objects - this issue is reproducible with the following script.
|
#8190 - fixed here. |
Fixed and released.. |
Using the MinIO Bosh releases we are unable to upgrade from version 2019-08-14 to 2019-08-21. We are using a deployment equivalent to the sample manifest provided in the bosh release repositoty: 4 VMs with 1 disk each.
Expected Behavior
Cluster should start successfully
Current Behavior
Cluster doesn't initialize and reports the following in the logs
Your Environment
uname -a
): Linux 8f6fb5cc-3b97-459a-a7f1-3a2386f79eda 4.15.0-55-generic Adding more api suite tests #60~16.04.2-Ubuntu SMP Thu Jul 4 09:03:09 UTC 2019 x86_64 x86_64 x86_64 GNU/LinuxError logs
The text was updated successfully, but these errors were encountered: