Project

General

Profile

Bug #17729

ceph-release rpms have changed names

Added by Zack Cerza over 7 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
% Done:

0%

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

Description

See:
http://pulpito.ceph.com/zack-2016-10-27_14:59:23-upgrade:jewel-x-master-distro-basic-smithi/498277/

Long story short:

$ curl -I https://chacra.ceph.com/r/ceph/jewel/3a9fba20ec743699b69bd0181dd6c54dc01c64b9/centos/7/flavors/default/noarch/ceph-release-1-0.el7.noarch.rpm
HTTP/1.1 404 Not Found
Server: nginx
Date: Thu, 27 Oct 2016 21:36:15 GMT
Content-Type: text/html
Content-Length: 162
Connection: keep-alive

$ curl -I http://gitbuilder.ceph.com/ceph-rpm-centos7-x86_64-basic/sha1/3a9fba20ec743699b69bd0181dd6c54dc01c64b9/noarch/ceph-release-1-0.el7.noarch.rpm
HTTP/1.1 200 OK
Date: Thu, 27 Oct 2016 21:31:22 GMT
Server: Apache/2.4.7 (Ubuntu)
Last-Modified: Thu, 21 Apr 2016 12:14:22 GMT
ETag: "b28-530fda682c380" 
Accept-Ranges: bytes
Content-Length: 2856
Content-Type: application/x-redhat-package-manager

It appears that chacra has ceph-release-1-1.el7.noarch.rpm for some reason.

That package, for RPM distros, at least, needs to be in a predictable location.

History

#2 Updated by Andrew Schoen over 7 years ago

This is a difference between the build scripts for upstream releases and testing repos.

That first link is from chacra.ceph.com, which is a repo made for our upstream releases, the other from 1.chacra.ceph.com would have been created for testing specifically.

I'm starting to wonder if we should not use chacra.ceph.com at all, we seem to keep stumbling across these little gotchas.

#3 Updated by Alfredo Deza over 7 years ago

Upstream releases use a 1-1 that got bumped from 1-0 in 2015.

For upstream, we cannot keep the same version for ever, it would prevent us from invalidating older/invalid RPMs. An example
of this is the centos-release rpms: https://rpmfind.net/linux/rpm2html/search.php?query=centos-release

To summarize:

- yes, it changed names in 2015.
- We should not provide the same file with the same version for ever.
- clients should accommodate for a newer version

#4 Updated by Andrew Schoen over 7 years ago

The version change is one problem, but the other is that repos created or imported into chacra.ceph.com will contain a ceph-release file that generates a ceph.repo that points to download.ceph.com, which is correct for our upstream builds but doesn't work for testing. Also, the ceph-release file from repos already living at gitbuilder.ceph.com will point back to gitbuilder.ceph.com so that file can't be imported into chacra.ceph.com for testing either.

After some discussion we think the best path forward is to have teuthology change the way it consumes repos from chacra nodes. I've added a feature to the /repos/ endpoint in chacra that will print out either a rpm repo file or deb source list. Teuthology and other clients can use this endpoint to consume chacra repos. This feature was introduced with: https://github.com/ceph/chacra/pull/212

To use, get a full API url to a chacra repo from shaman output (as ``chacra_url``) or otherwise and add '/repo/' to the end.

For example, this is the output from the repo used in the summary:

$ curl https://chacra.ceph.com/repos/ceph/jewel/3a9fba20ec743699b69bd0181dd6c54dc01c64b9/centos/7/flavors/default/repo/
[ceph]
name=ceph packages for \$basearch
baseurl=https://chacra.ceph.com/r/ceph/jewel/3a9fba20ec743699b69bd0181dd6c54dc01c64b9/centos/7/flavors/default/\$basearch
enabled=1
gpgcheck=0
type=rpm-md

[ceph-noarch]
name=ceph noarch packages
baseurl=https://chacra.ceph.com/r/ceph/jewel/3a9fba20ec743699b69bd0181dd6c54dc01c64b9/centos/7/flavors/default/noarch
enabled=1
gpgcheck=0
type=rpm-md

[ceph-source]
name=ceph source packages
baseurl=https://chacra.ceph.com/r/ceph/jewel/3a9fba20ec743699b69bd0181dd6c54dc01c64b9/centos/7/flavors/default/SRPMS
enabled=1
gpgcheck=0
type=rpm-md

#5 Updated by Andrew Schoen over 7 years ago

  • Status changed from New to Resolved

This was resolved by using the new repo file generation feature in chacra.

Also available in: Atom PDF