Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1257050 - Missing information about firewalld service in Satellite 6.1 and 6.0 documentation
Summary: Missing information about firewalld service in Satellite 6.1 and 6.0 document...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs API Guide
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite-doc-list
QA Contact: satellite-doc-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-26 07:25 UTC by Marcel Gazdík
Modified: 2019-09-26 17:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-24 04:24:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Marcel Gazdík 2015-08-26 07:25:08 UTC 
Document URL: 
https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Installation_Guide/sect-Red_Hat_Satellite-Installation_Guide-Prerequisites.html#form-Red_Hat_Satellite-Installation_Guide-Prerequisites-Required_Network_Ports

Section Number and Name: 
1.4.5. Required Network Ports
  |- Procedure 1.1
    |- B 


Describe the issue: 
In the section A of the procedure mentioned above, there is information about how to check if the firewall is running or not. But this information is not provided for RHEL 7 FirewallD as this service is different some of the customers can be confused.

Suggestions for improvement: 
Add similar section for the RHEL7 FirewallD

Make sure the firewalld service is started and enabled:
# systemctl start firewalld
# systemctl enable firewalld 

# systemctl start firewalld status
# firewalld.service - firewalld - dynamic firewall daemon
#    Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)
#    Active: inactive (dead) since Wed 2015-08-26 08:58:25 CEST; 23min ago
#  Main PID: 582 (code=exited, status=0/SUCCESS)
#    CGroup: /system.slice/firewalld.service

Commands: 1) start the service
          2) enable the service during boot
          3) example of status when the service is enabled

Additional information:
Comment 1 Stephen Wadeley 2015-12-10 22:24:33 UTC 
Thank you for raising this bug
Comment 2 Andrew Dahms 2016-10-24 04:24:00 UTC 
Hi Marcel,

Thank you for raising this bug.

Instructions on how to set up the firewall on RHEL 7 systems using firewall-cmd are now available in the Satellite 6.2 documentation in locations such as the following -

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/single/installation-guide#enabling_client_connections_to_satellite

Work on the Satellite documentation is currently focusing on the 6.2 version, so we do not have any plans to backport this content at current. I will close this bug for now, but please let us know if you have any further concerns.

Kind regards,

Andrew
Note You need to log in before you can comment on or make changes to this bug.