Bug 1379543 - Enable gdeploy to check if firewalld service is started before opening the ports.
Summary: Enable gdeploy to check if firewalld service is started before opening the po...
Keywords:
Status: CLOSED DUPLICATE of bug 1362570
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: gdeploy
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Sachidananda Urs
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-27 05:41 UTC by RamaKasturi
Modified: 2019-04-03 10:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-27 06:04:38 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description RamaKasturi 2016-09-27 05:41:57 UTC 
Description of problem:
If user is using a  platform where firewalld service is started by default then gdeploy will open the ports with out any issues.In an environment like RHEV-H firewalld is not started by default and due to this gdeploy fails to open the ports. gdeploy should have a functionality to check if service started before it tries to open the ports.

Version-Release number of selected component (if applicable):
gdeploy-2.0-16.el7rhgs.noarch

How reproducible:
Always

Steps to Reproduce:
1. Install RHEV-H from ISO
2. Install ansible and gdeploy packages
3. Run robo.conf from one of the node.

Actual results:
gdeploy fails to open the firewalld ports since firewalld service is not started.

Expected results:
gdeploy should check if service is started before opening the ports.

Additional info:
Comment 2 Sachidananda Urs 2016-09-27 05:54:43 UTC 
Kasturi, there is already a bug for this: https://bugzilla.redhat.com/show_bug.cgi?id=1362570 and fixed in latest release. Please review and mark this as duplicate, if it is hte same bug.
Comment 3 RamaKasturi 2016-09-27 06:04:38 UTC 
Thanks sachi. I will close this bug.

*** This bug has been marked as a duplicate of bug 1362570 ***
Note You need to log in before you can comment on or make changes to this bug.