Project

General

Profile

Actions

Bug #5658

open

sporadic failures when cloning from https://git.osmocom.org/

Added by fixeria 4 months ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
-
Start date:
08/23/2022
Due date:
% Done:

0%

Spec Reference:

Description

Recently we migrated our osmo-ci infrastructure from git:// to https://

https://gerrit.osmocom.org/c/osmo-ci/+/28349 [MERGED]

and immediately after that we started to observe sporadic git-clone failures in master Jenkins jobs like:

+ git clone https://git.osmocom.org/libosmo-abis libosmo-abis
Cloning into 'libosmo-abis'...
error:  (curl_result = 56, http_code = 200, sha1 = 6498826eae07a02be1afc8e4f161bd1caa626e7d)
error: Unable to find 6498826eae07a02be1afc8e4f161bd1caa626e7d under https://git.osmocom.org/libosmo-abis
Cannot obtain needed tree 6498826eae07a02be1afc8e4f161bd1caa626e7d
while processing commit e58d33153dd2bed3629b9a09fd6add58f296bd6a.
error: fetch failed.

+ git clone https://git.osmocom.org/libosmo-sccp libosmo-sccp
Cloning into 'libosmo-sccp'...
error: HTTP/2 stream 0 was closed cleanly, but before getting  all response header fields, treated as error (curl_result = 92, http_code = 0, sha1 = 80f1e4bfb9c161c76f04443bd03b8a2c3ce7dbd5)
error: HTTP/2 stream 0 was closed cleanly, but before getting  all response header fields, treated as error (curl_result = 92, http_code = 0, sha1 = 7be9bdd1632efe63b9af2d42dd355eda7883747c)
error: Unable to find 7be9bdd1632efe63b9af2d42dd355eda7883747c under https://git.osmocom.org/libosmo-sccp
Cannot obtain needed blob 7be9bdd1632efe63b9af2d42dd355eda7883747c
while processing commit e7c8067df026fd294af2c95fbd2ceb16eeab7d74.
error: fetch failed.

In the last few days only master-openbsc is affected (failing to clone libosmo-sccp):

https://jenkins.osmocom.org/jenkins/view/master/job/master-openbsc/12429/
https://jenkins.osmocom.org/jenkins/view/master/job/master-openbsc/12418/
https://jenkins.osmocom.org/jenkins/view/master/job/master-openbsc/12414/


Related issues

Related to Cellular Network Infrastructure - Bug #5670: git.osmocom.org: cloning via https:// is slowResolvedlaforge08/31/2022

Actions
Actions #2

Updated by osmith 4 months ago

workaround to clone from gerrit was merged: https://gerrit.osmocom.org/c/osmo-ci/+/29191

Actions #3

Updated by fixeria 4 months ago

https://jenkins.osmocom.org/jenkins/view/master/job/master-osmo-trx/4513/

+ test -d libosmocore
+ cd libosmocore
+ git fetch --tags origin
fatal: unable to access 'https://git.osmocom.org/libosmocore/': gnutls_handshake() failed: The TLS connection was non-properly terminated.
Build step 'Execute shell' marked build as failure
Actions #4

Updated by laforge 3 months ago

  • Subject changed from sporading failures when cloning from https://git.osmocom.org/ to sporadic failures when cloning from https://git.osmocom.org/
Actions #5

Updated by laforge 3 months ago

I think in order to really debug those we would need to know the ostname / source-ip exact timestamps to check the nginx logs at the given point in time.

Given the sporadic nature I cannot reproduce this at all locally - and without knowing what to look for I cannot really find anything useful in the logs.

Actions #6

Updated by fixeria 3 months ago

  • Related to Bug #5670: git.osmocom.org: cloning via https:// is slow added
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)