Bug #8734
closedEPEL / Ceph.com package priority issues
0%
Description
When following the Ceph.com manual configuration guide in our documentation you can fall into a trap if you have an EPEL repository configured, which will be the case for many people. If a system is configured to use EPEL repositories then Ceph packages from EPEL will take preference over our packages. This is further complicated because the metadata that is used to build the EPEL packages omits directories in /var/lib/ceph that are expected to exist by tools like ceph-mon (for creation) and ceph-disk (for activation).
The suggested work around should be to install the 'yum-plugin-preferences' package and update the Ceph.com repos in /etc/yum.repos.d to include "priority=2" statements.
Updated by Sage Weil almost 10 years ago
- Project changed from Ceph to devops
- Category deleted (
documentation)
Updated by Sage Weil almost 10 years ago
- Assignee set to John Wilkins
- Source changed from other to Development
Updated by Sage Weil over 9 years ago
- Status changed from New to 12
ceph-deploy sets the priority; other users will need to do so themselves.
perhaps that can be mentioned in the docs? then/otherwise, let's close
Updated by John Wilkins over 9 years ago
- Status changed from In Progress to Resolved
I added priorty=2 to the get packages document example for ceph.repo. I also added an install yum-priorities series of steps for manually installing ceph RPMs.