Project

General

Profile

Actions

Bug #6746

closed

ceph-release rpm not playing well with yum-plugin-priorities

Added by John Kinsella over 10 years ago. Updated almost 10 years ago.

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

0%

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

Description

We use the yum-plugin-priorities to organize things across 10ish public/private repos we define on our servers. Just notice that "ceph-deploy install" wasn't installing the latest ceph on a target server...the epel repo had a priority defined, so yum was grabbing ceph from epel instead of the ceph repo.

We can work around this by defining "exclude=ceph*,python-ceph*,libceph*,librbd*" but might want to consider either documenting or putting a priority definition in the ceph repo.

Actions #1

Updated by John Kinsella over 10 years ago

whoops sorry this isn't really devops related. feel free to move...

Actions #2

Updated by Ian Colle over 10 years ago

  • Assignee set to Anonymous
Actions #3

Updated by Ken Dreyer over 10 years ago

  • Assignee changed from Anonymous to Ken Dreyer

Hi John, What priority value would work for you?

Actions #4

Updated by John Kinsella over 10 years ago

Ken - hard to say...it's a fairly important repo so I'd say 2 or 3 on our 10 point scale, but I suspect this varies from site to site. Maybe have a default value, and let users override when calling ceph-deploy?

Actions #5

Updated by Ian Colle about 10 years ago

  • Assignee deleted (Ken Dreyer)
Actions #6

Updated by Alfredo Deza almost 10 years ago

  • Status changed from New to Resolved

you can now specify the repository information when installing and just apply whatever priority you need in the config.

See http://ceph.com/ceph-deploy/docs/conf.html

Actions

Also available in: Atom PDF