Project

General

Profile

Actions

Bug #24743

closed

ceph v12.2.5 is not available in shaman.ceph.com

Added by Yuri Weinstein almost 6 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Urgent
% Done:

0%

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

Description

Run: http://pulpito.ceph.com/teuthology-2018-07-01_05:30:02-upgrade:luminous-p2p-luminous-distro-basic-smithi/
Jobs: all
Logs: http://qa-proxy.ceph.com/teuthology/teuthology-2018-07-01_05:30:02-upgrade:luminous-p2p-luminous-distro-basic-smithi/2727635/teuthology.log

2018-07-02T07:29:31.324 DEBUG:teuthology.repo_utils:git ls-remote git://git.ceph.com/ceph v12.2.5^{} -> cad919881333ac92274171586c827e01f554a70a
2018-07-02T07:29:31.326 DEBUG:teuthology.packaging:Querying https://shaman.ceph.com/api/search?status=ready&project=ceph&flavor=default&distros=centos%2F7%2Fx86_64&sha1=cad919881333ac92274171586c827e01f554a70a
2018-07-02T07:29:31.565 ERROR:teuthology.run_tasks:Saw exception from tasks.
Traceback (most recent call last):
  File "/home/teuthworker/src/git.ceph.com_git_teuthology_master/teuthology/run_tasks.py", line 89, in run_tasks
    manager.__enter__()
  File "/usr/lib/python2.7/contextlib.py", line 17, in __enter__
    return self.gen.next()
  File "/home/teuthworker/src/git.ceph.com_git_teuthology_master/teuthology/task/install/__init__.py", line 437, in upgrade
    upgrade_common(ctx, config, upgrade_old_style)
  File "/home/teuthworker/src/git.ceph.com_git_teuthology_master/teuthology/task/install/__init__.py", line 369, in upgrade_common
    upgrade_version = get_upgrade_version(ctx, node, remote)
  File "/home/teuthworker/src/git.ceph.com_git_teuthology_master/teuthology/task/install/__init__.py", line 25, in get_upgrade_version
    version = builder.version
  File "/home/teuthworker/src/git.ceph.com_git_teuthology_master/teuthology/packaging.py", line 539, in version
    self._version = self._get_package_version()
  File "/home/teuthworker/src/git.ceph.com_git_teuthology_master/teuthology/packaging.py", line 946, in _get_package_version
    self.assert_result()
  File "/home/teuthworker/src/git.ceph.com_git_teuthology_master/teuthology/packaging.py", line 928, in assert_result
    raise VersionNotFoundError(self._result.url)
VersionNotFoundError: Failed to fetch package version from https://shaman.ceph.com/api/search/?status=ready&project=ceph&flavor=default&distros=centos%2F7%2Fx86_64&sha1=cad919881333ac92274171586c827e01f554a70a

Related issues 1 (0 open1 closed)

Related to teuthology - Feature #24760: Add ability to check/install (/from) chacra.ceph.com and/or download.ceph.com for released ceph versionsResolvedZack Cerza07/03/2018

Actions
Actions #1

Updated by Alfredo Deza almost 6 years ago

You are using this in a way that it wasn't thought about. Shaman builds are "development builds" and they get purged. They aren't kept forever.
The system produces on average ~300 repos per day, we can't possibly keep them around for ever
so , these rules allows to fine tune the purging of repos. In the case of the "luminous" branch, we understand it is needed for testing that release branch, so the rules say that we keep the repos for 14 days
but we always must have at least 10
that means that if you had your sha1 from 12.2.5 around recently, that some newer builds were produced for Luminous that pushed the sha1 for 12.2.5 out
(think of it as a first-in-last-out queue)
if you want to test against a release then you must use download.ceph.com
I don't know the internals or why is it that you can't use download.ceph.com
in the case that you need some other version which is not the latest (e.g. 12.2.4 instead of 12.2.5) then you can use chacra.ceph.com
those are where releases don't expire, and are kept forever

Actions #2

Updated by Yuri Weinstein almost 6 years ago

  • Related to Feature #24760: Add ability to check/install (/from) chacra.ceph.com and/or download.ceph.com for released ceph versions added
Actions #3

Updated by Nathan Cutler almost 6 years ago

  • Assignee set to David Galloway

@David Galloway can you please trigger a build of cad919881333ac92274171586c827e01f554a70a (v12.2.5 tag) and put the resulting repo on the chacra node that doesn't continually purge itself?

Thanks.

Actions #4

Updated by Nathan Cutler almost 6 years ago

  • Project changed from Ceph to CI
Actions #5

Updated by Nathan Cutler almost 6 years ago

The test yaml in question is just:

  - install.upgrade:
      mon.a:
        tag: v12.2.5
      mon.b:
        tag: v12.2.5

This works for other release tags, but ISTR making it work (i.e. ensuring the chacra repos don't get purged) is a manual process. Correct, David?

Actions #6

Updated by David Galloway almost 6 years ago

I'm in the Alfredo school of thought on this one. cad91988 is an official release and /is/ on the chacra node that doesn't get cleaned up. The problem is teuthology can't translate/locate tag -> sha1 -> chacra.ceph.com path.

https://chacra.ceph.com/r/ceph/luminous/cad919881333ac92274171586c827e01f554a70a/

I think what I've done in the past is synced from chacra.ceph.com or download.ceph.com to a dev node so that teuthology can find the repos via shaman but this is time consuming, hacky, and the build will eventually get cleaned up again.

Actions #7

Updated by David Galloway over 3 years ago

  • Status changed from New to Resolved

I think we just informed shaman of the permanent chacra node.

Actions

Also available in: Atom PDF