-
Notifications
You must be signed in to change notification settings - Fork 0
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
Ingest Ladybird checksums into DCS for validation purposes #2963
Comments
All checksum from Ladybird are in /data/10 on the management-workers. The files are tsv format:
You can ignore filename and label. The filenames are |
Deployed to Test with release v2.72.9 |
Do any of them have a sha256_checksum or md5_checksum?
|
Taking back to In Progress. Next Steps post pairing Martin and Kait: rake task:
integrity check:
decide which checksum attribute will be 'source of truth':
|
Run rask task in UAT on Tuesday, November 26 at end of day, 5 pm ET. |
Ticket to run rake task on prod - #2973 |
PR ready for review - yalelibrary/yul-dc-management#1459 |
Deployed to Test with release v2.73.1 |
PR ready for review - yalelibrary/yul-dc-management#1461 |
Deployed to Test with release v2.73.4 |
working on Test. Will promote to UAT. |
Are the data shares at yale set up the same way on UAT as the are on Test? Asking if I need to update where the rake task thinks the tsv files to be. |
They are the same for test and uat/prod. So, run the rake task the same way. (Same path to files) |
Running on UAT with
|
The workers were restared at December 16, 2024 at 14:20.
|
It finished! Logs are in |
Story
Prior to completing the work in #2962, we will need to ingest the Ladybird image checksums into DCS storage.
Acceptance
The text was updated successfully, but these errors were encountered: