Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 2090239

Summary: firewall need to be reloaded to Configuring remote monitoring access
Product: Red Hat Enterprise Linux 9 Reporter: justsomeone <nameless0001>
Component: DocumentationAssignee: Mariya Pershina <mpershin>
Documentation sub component: default QA Contact:
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: unspecified    
Priority: high CC: egarver, mlichvar, rhel-docs
Version: 9.0Keywords: Documentation
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-08 10:34:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description justsomeone 2022-05-25 12:34:01 UTC 
Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_basic_system_settings/using-chrony_configuring-basic-system-settings


Section Number and Name: 

28.5. Configuring remote monitoring access

Describe the issue: 

step 3 of the procedure should be followed by 

firewall-cmd --reload 

so the change take effect

hope that help and have a nice day :)
Comment 2 Miroslav Lichvar 2022-06-07 12:02:36 UTC 
If I understand it correctly, the reload command is necessary only after making changes to the permanent configuration, that is in the second part of the step 3. You might want to check that with firewalld maintainers.
Comment 6 justsomeone 2022-06-07 14:53:11 UTC 
(In reply to Miroslav Lichvar from comment #2)
> If I understand it correctly, the reload command is necessary only after
> making changes to the permanent configuration, that is in the second part of
> the step 3. You might want to check that with firewalld maintainers.

thanks Miroslav

and that what written in step 3

 Open port 323 in the firewall to connect from a remote system.

#  firewall-cmd --zone=public --add-port=323/udp

If you want to open port 323 permanently, use the --permanent.

#  firewall-cmd --permanent --zone=public --add-port=323/udp

so the permanent option is there

by the way i am still learning so i could miss something so if i did then sorry for wasting your time 

thanks again and have a nice day :)
Comment 7 Mariya Pershina 2022-06-08 10:34:52 UTC 
We clarified the procedure, and the fix is now visible on the Customer Portal:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_basic_system_settings/using-chrony_configuring-basic-system-settings#proc_configuring-remote-monitoring-access_using-chrony 

Thanks everyone for your help!
Comment 8 justsomeone 2022-06-08 10:56:31 UTC 
(In reply to Mariya Pershina from comment #7)
> We clarified the procedure, and the fix is now visible on the Customer
> Portal:
> 
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/
> html/configuring_basic_system_settings/using-chrony_configuring-basic-system-
> settings#proc_configuring-remote-monitoring-access_using-chrony 
> 
> Thanks everyone for your help!

thanks for both of you and for the whole team