Description of problem: RHV 4.2 requires ovirt-host rpm to be available on the servers in order to manage. The ovirt-host rpm needs to be available in RHGS 3.3 channels Version-Release number of selected component (if applicable): 3.3 How reproducible: NA Additional info:
@Sahina, As this bug is already fixed and ovirt-host package is available could you move this bug to ON_QA for verification.
Tested with RHGS 3.3.1 ( glusterfs-3.8.4-54.8.el7rhgs ) and with other components as follows: ovirt-host-3.6.0-1.el7rhgs.noarch vdsm-4.17.33-1.2.el7rhgs.noarch RHV Manager :4.2.3.8-0.1.el7 RHGS 3.3.1 nodes and volumes could be managed in RHV 4.2.3
(In reply to SATHEESARAN from comment #1) > @Sahina, As this bug is already fixed and ovirt-host package is available > could you move this bug to ON_QA for verification. Moving this bug ON_QA as the required ovirt-host package is already in place
Verifying this bug with comment2
(In reply to SATHEESARAN from comment #2) > Tested with RHGS 3.3.1 ( glusterfs-3.8.4-54.8.el7rhgs ) and with other > components as follows: > ovirt-host-3.6.0-1.el7rhgs.noarch > vdsm-4.17.33-1.2.el7rhgs.noarch > RHV Manager :4.2.3.8-0.1.el7 > > RHGS 3.3.1 nodes and volumes could be managed in RHV 4.2.3 Missed to add clarity on DC/Cluster compatibility. All these verification done by adding RHGS to DC/Cluster compatibility 3.6 in RHV 4.2
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-2018:1832