Bug 1674580 - Validate gluster, vdo, firewalld and chronyd services running
Summary: Validate gluster, vdo, firewalld and chronyd services running
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-ansible
Version: rhhiv-1.6
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: ---
: RHGS 3.4.z Batch Update 4
Assignee: Sachidananda Urs
QA Contact: Mugdha Soni
URL:
Whiteboard:
Depends On:
Blocks: 1674572
TreeView+ depends on / blocked
 
Reported: 2019-02-11 16:25 UTC by Gobinda Das
Modified: 2019-03-27 03:44 UTC (History)
6 users (show)

Fixed In Version: gluster-ansible-infra-1.0.3-2.el7rhgs, gluster-ansible-features-1.0.4-3.el7rhgs
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1674572
Environment:
Last Closed: 2019-03-27 03:44:39 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0661 0 None None None 2019-03-27 03:44:53 UTC

Comment 2 Sachidananda Urs 2019-02-19 11:06:55 UTC 
Patches: https://github.com/gluster/gluster-ansible-features/pull/20
Comment 4 Mugdha Soni 2019-02-25 10:52:46 UTC 
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 were being enabled and gluster deployment was successful.

Hence,moving the bug to verified state.
Comment 6 errata-xmlrpc 2019-03-27 03:44:39 UTC 
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-2019:0661
Note You need to log in before you can comment on or make changes to this bug.