+++ This bug was initially created as a clone of Bug #1466054 +++ Description of problem: RHEL Base ships one version of Ceph (Hammer), and the RH Ceph Storage layered product ships other versions of Ceph. Sometimes these versions do not align. If a customer is on an older layered product version, and we add a newer version to RHEL base, this will break that customer's setup. The only workaround is to upgrade prematurely. Version-Release number of selected component (if applicable): RHCEPH 1.3, 2.3, 3.0 Steps to Reproduce: 1. Install RHCEPH 1.3 (eg. ceph-mon-0.94.something) 2. Enable a RHEL 7 Base repo that includes a newer ceph-common update. One example is http://download.engineering.redhat.com/released/RHEL-7/7.4-Beta/Server/x86_64/os/ , which has has ceph-common-10.2.something 3. Run yum update Actual results: Yum errors Expected results: Yum does not error and does not attempt to replace the customer's RHCEPH 1.3 packages. Additional info: To handle this, we are going to bump the ceph package's epoch across all RHCEPH product versions. This will make RHCEPH's builds always override RHEL Base (and even upstream).
QE team: to verify this bugfix in RHCEPH 2: 1. Sanity test installs and upgrades: Basic installs must succeed on RHEL 7.3 and 7.4 Upgrades from RHCEPH 1.3 to RHCEPH 2 must succeed on RHEL 7.3 and 7.4 2. Examine the package's epoch with "--qf": rpm -q ceph-common --qf "%{epoch}:%{name}-%{version}-%{release}\n" It should print "2:ceph-common" for the RHCEPH layered product's packages, and "1:ceph-common" for RHEL Base's packages.
1. Upgrade from 2.3+RHEL 7.3 ====> 2.4+RHEL7.4 is successful. 2. For layered product install [ubuntu@magna035 ~]$ rpm -q ceph-common --qf "%{epoch}:%{name}-%{version}-%{release}\n" 2:ceph-common-10.2.7-32.el7cp 3. For install from rhel7-server-rpm channel [ubuntu@magna117 ~]$ rpm -q ceph-common --qf "%{epoch}:%{name}-%{version}-%{release}\n" 1:ceph-common-0.94.5-2.el7 Hence marking this as verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2640