Project

General

Profile

Actions
Copy link

Bug #63959

open

sha256sum mismatch for boost_1_82_0.tar.bz2 in Shaman builds

Added by Laura Flores 4 months ago. Updated 4 months ago.

Status:
Pending Backport
Priority:
Normal
Assignee:
Casey Bodley
% Done:

0%

Source:
Tags:
backport_processed
Backport:
pacific quincy reef
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):

Description

Description of problem

The boost jfrog mirror is broken and returns an HTML error page instead of the archive. The file size of this page is 11534 bytes.

When download_from() retries the download from download.ceph.com, the -c option tells it to resume the download of the existing file. The resulting boost_1_82_0.tar.bz2 ends up with the correct total file size of 121325129 bytes, but the first 11534 bytes still correspond to the HTML from jfrog. that causes the sha256sum mismatch.

How to reproduce

Steps:

  1. Trigger a build by pushing a branch to ceph-ci
  2. Observe the build fail in the "ceph-dev-new-setup" step in the Jenkins workflow: https://jenkins.ceph.com/job/ceph-dev-new-setup/

Time noticed / Event Window (in UTC)

Started happening about a day ago.

Actual results

~/ceph$ ./make-dist
...
2024-01-08 08:14:08 URL:https://landing.jfrog.com/reactivate-server/boostorg [11534/11534] -> "boost_1_82_0.tar.bz2" [1]            
Error: failed to download boost_1_82_0.tar.bz2: SHA256 mismatch.                                                                    
2024-01-08 08:14:13 URL:https://download.ceph.com/qa/boost_1_82_0.tar.bz2 [121325129/121325129] -> "boost_1_82_0.tar.bz2" [1]       
Error: failed to download boost_1_82_0.tar.bz2: SHA256 mismatch.                                                                    
Error: failed to download boost_1_82_0.tar.bz2.

~/ceph$ ls -l boost_1_82_0.tar.bz2 
-rw-rw-r-- 1 cbodley cbodley 121325129 Jun 23  2023 boost_1_82_0.tar.bz2

~/ceph$ sha256sum boost_1_82_0.tar.bz2 
c924dd5cf654a3e72e0d61138406f150c3c17cfab8bf9c120682d4c0e5338c44  boost_1_82_0.tar.bz2

~/ceph$ head -n 1 boost_1_82_0.tar.bz2 
<!DOCTYPE html><html lang="en"><head><meta charset="utf-8"><meta http-equiv="X-UA-Compatible" content="IE=edge"><meta name="viewport" content="width=device-width,initial-scale=1"><link rel="icon" href="/favicon.ico"><title>JFrog Landing</title><link href="https://fonts.googleapis.com/css?family=Open+Sans:400,700,800&display=swap" rel="stylesheet"><script>VERSION = "2023.11.248";

Expected results

Successful download of boost.

Additional analysis

The fix involves removing the -c option so that wget fetches the archive in its entirety.

Related issues 3 (0 open — 3 closed)

Copied to Ceph - Backport #63963: pacific: sha256sum mismatch for boost_1_82_0.tar.bz2 in Shaman buildsResolvedCasey BodleyActions
Copied to Ceph - Backport #63964: reef: sha256sum mismatch for boost_1_82_0.tar.bz2 in Shaman buildsResolvedCasey BodleyActions
Copied to Ceph - Backport #63965: quincy: sha256sum mismatch for boost_1_82_0.tar.bz2 in Shaman buildsResolvedCasey BodleyActions
Actions
Copy link
 #1

Updated by Laura Flores 4 months ago

  • Subject changed from <short description of problem> to sha256sum mismatch for boost_1_82_0.tar.bz2 in Shaman builds
Actions
Copy link
 #2

Updated by Laura Flores 4 months ago

  • Status changed from New to Fix Under Review
Actions
Copy link
 #4

Updated by Casey Bodley 4 months ago

  • Backport set to pacific quincy reef
Actions
Copy link
 #5

Updated by Casey Bodley 4 months ago

sharing some context from the Boost mailing list:

[boost] Boost downloads and JFrog1

Rather than emails and Slack DMs, I would prefer we have this discussion
on the mailing list.

To summarize what I have repeated in the aforementioned channels:

- Yes, our downloads are not working again because the JFrog account is
again not active.
- No, I cannot do anything about the JFrog account.
- Yes, we can update the website to point to downloads hosted elsewhere.

It is correct that JFrog does not charge us yet but our traffic has
increased from 60TB/month to almost 200TB/month which is no longer
supportable for free. We have limited time to find a solution.

We are on borrowed time but as far as I know we still have time. the
deactivation of the JFrog account in December 31 was not expected, and it
was reinstated.

[1] https://lists.boost.org/Archives/boost//2024/01/255654.php

Actions
Copy link
 #6

Updated by Laura Flores 4 months ago

  • Status changed from Fix Under Review to Pending Backport
Actions
Copy link
 #7

Updated by Casey Bodley 4 months ago

  • Assignee set to Casey Bodley
Actions
Copy link
 #8

Updated by Casey Bodley 4 months ago

  • Project changed from Infrastructure to Ceph

the backport-create-issue script only seems to work for issues in the Ceph project, so moving it temporily

Actions
Copy link
 #9

Updated by Casey Bodley 4 months ago

  • Copied to Backport #63963: pacific: sha256sum mismatch for boost_1_82_0.tar.bz2 in Shaman builds added
Actions
Copy link
 #10

Updated by Casey Bodley 4 months ago

  • Copied to Backport #63964: reef: sha256sum mismatch for boost_1_82_0.tar.bz2 in Shaman builds added
Actions
Copy link
 #11

Updated by Casey Bodley 4 months ago

  • Copied to Backport #63965: quincy: sha256sum mismatch for boost_1_82_0.tar.bz2 in Shaman builds added
Actions
Copy link
 #12

Updated by Casey Bodley 4 months ago

  • Tags set to backport_processed
Actions
Copy link
 #13

Updated by Casey Bodley 4 months ago

  • Project changed from Ceph to Infrastructure
Actions
Copy link
 #14

Updated by Casey Bodley 4 months ago

  • Project changed from Infrastructure to Ceph
  • Pull request ID set to 55088
Actions
Copy link
 #15

Updated by Casey Bodley 4 months ago

  • Project changed from Ceph to Infrastructure
Actions
Copy link

Also available in: Atom PDF