Description of problem:
Ceph's sub-package version dependencies are looser than they need to be. This means someone could install a slightly newer version of "ceph-common" than "ceph".

Ideally this would not happen, and customers would always subscribe to all the correct repositories and "yum update" all packages at the same time. But this doesn't always happen. Currently it is possible that if a customer uses yum to update

Version-Release number of selected component (if applicable):
RHCS 1.3.1

How reproducible:
Depends on customer's steps (whether they've subscribed to all appropriate repos and run "yum update" without additional arguments).

Steps to Reproduce:
1. Select a plain RHEL 7 Server node to be a Ceph OSD.

2. Ensure the node is *not* subscribed to rhel-7-server-rhceph-1.3-osd-rpms or any other ceph repo in subscription-manager, like rhel-7-server-rhceph-1.3-tools-rpms.

3. Install the ceph-osd package from the RHCS 1.3.0 ISO. `rpm -qv ceph-osd` should show ceph-osd-0.94.1-13.el7cp.

(Note, I'm using RHCS 1.3.0 in this example, so that it will be easy to test a "yum update" in the next steps. But this affects the package set in RHCS 1.3.1 as well.)

4. Subscribe the node to the OSD repo in the CDN:
   sudo subscription-manager repos --enable=rhel-7-server-rhceph-1.3-osd-rpms

5. Run `yum update ceph-common-0.94.1-19.el7cp` on the OSD node. The key here is that the version (0.94.1) stays the same, but the Release field (-19) is different.

Actual results:
Yum updates ceph-common without updating "ceph" and "ceph-osd".

Expected results:
Yum should update all ceph subpackages when the user tries to update any one sub-package.