Hide Forgot
Description of problem: The channels listed in the documentation do not include rh-common. Minor versions of glusterfs are incompatible, so the clients (RHEV) need to update via rh-common. Version-Release number of selected component (if applicable):3.6
Did we say this is not needed?
No, but other docs call out rh-common as a needed channel. There should at least be a note that the minor release of glusterfs included in the RHEV channel may not be compatible with the latest glusterfs. Currently some volume operations are not possible using RHEV 3.6 and RHGS 3.1.2, though both were released the same week. The best method is to update glusterfs via rh-common. In environments where documentation is heavily relied upon adding rh-common when not explicitly named can cause unnecessary cases. See http://review.gluster.org/#/c/5786/
Any update should be included in RHEV channel via multi errata.
RHEV channel is an entitlement, which is $$$. I brought this up in gluster-prio-list and received the following from gluster SME " I would recommend to subscribe to rh-common for their RHEV/RHEL environment. It is already in RHGS doc, May be a doc bug in RHEL/RHEV should add these recommendation."
(In reply to Tupper Cole from comment #4) > RHEV channel is an entitlement, which is $$$. I brought this up in > gluster-prio-list and received the following from gluster SME > > " > I would recommend to subscribe to rh-common for their RHEV/RHEL environment. > > It is already in RHGS doc, May be a doc bug in RHEL/RHEV should add these > recommendation." I'm not sure what you mean. Your customer is not a RHEV customer?