Description of problem: Now there is no check whether gluster, vdo, firewalld and chronyd services running or not Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Need to validate all services. Additional info:
> > Expected results: > Need to validate all services. > We can enable and start them in the pre-requisites.
The dependent bug is ON_QA and moving this too
Tested it with the following:- 1. rhvh-4.3.0.5-0.20190221 2.glusterfs-server-3.12.2-45.el7rhgs 3.cockpit-ovirt-dashboard-0.12.2-1.el7ev 4.gluster-ansible-cluster-1.0-1.el7rhgs.noarch gluster-ansible-features-1.0.4-3.el7rhgs.noarch gluster-ansible-maintenance-1.0.1-1.el7rhgs.noarch gluster-ansible-infra-1.0.3-2.el7rhgs.noarch gluster-ansible-roles-1.0.4-1.el7rhgs.noarch gluster-ansible-repositories-1.0-1.el7rhgs.noarch Disabled the gluster ,chronyd ,firewall services before proceeding with gluster deployment.While the gluster deployemnt was in progress ,could see the firewall,VDO ,chroynd and gluster services being enabled and gluster deployment was successful. Hence,moving the bug to verified state.
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/RHEA-2019:1121