Project

General

Profile

Actions
Copy link

Bug #57914

closed

centos 8 build failed

Added by Yuri Weinstein over 1 year ago. Updated 7 months ago.

Status:
Resolved
Priority:
Urgent
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

I see it on main and pacific

https://jenkins.ceph.com/job/ceph-dev-build/ARCH=x86_64,AVAILABLE_ARCH=x86_64,AVAILABLE_DIST=centos8,DIST=centos8,MACHINE_SIZE=gigantic/50723//consoleFull

https://jenkins.ceph.com/job/ceph-dev-new-build/ARCH=x86_64,AVAILABLE_ARCH=x86_64,AVAILABLE_DIST=centos8,DIST=centos8,MACHINE_SIZE=gigantic/66113//consoleFull

-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
Actions
Copy link
 #1

Updated by Casey Bodley over 1 year ago

from those logs, i see the builds succeeding. at the end of both, i see:

Error: authenticating creds for "quay.ceph.io": pinging container registry quay.ceph.io: Get "https://quay.ceph.io/v2/": dial tcp 8.43.84.141:443: i/o timeout

Actions
Copy link
 #2

Updated by Yuri Weinstein over 1 year ago

All branches failed the same way

Actions
Copy link
 #3

Updated by Neha Ojha over 1 year ago

  • Priority changed from Normal to Urgent
Actions
Copy link
 #4

Updated by Laura Flores over 1 year ago

Note from Dan:

It's looking more and more like we're just going to have to rebuild these broken VMs from scratch. Luckily in many cases that won't involve complete data loss.

Actions
Copy link
 #5

Updated by Laura Flores 7 months ago

  • Status changed from New to Resolved
Actions
Copy link

Also available in: Atom PDF