Bug 1674580
| Summary: | Validate gluster, vdo, firewalld and chronyd services running | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Gobinda Das <godas> |
| Component: | gluster-ansible | Assignee: | Sachidananda Urs <surs> |
| Status: | CLOSED ERRATA | QA Contact: | Mugdha Soni <musoni> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | rhhiv-1.6 | CC: | musoni, rcyriac, rhs-bugs, sabose, sankarshan, sasundar |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 3.4.z Batch Update 4 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| 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: | Story Points: | --- | |
| Clone Of: | 1674572 | Environment: | |
| Last Closed: | 2019-03-27 03:44:39 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1674572 | ||
|
Comment 2
Sachidananda Urs
2019-02-19 11:06:55 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. 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 |