openstack/openstack-ansible
Code Issues Proposed changes

Clarify firewall rule check

Browse Source 
Replace the iptables-specific wording with a general firewall rules check.

Change-Id: I6d6a2c6aebb9b47193c6e5d40ff8c86c0644d816
Signed-off-by: Dmitriy Chubinidze <dcu995@gmail.com>
This commit is contained in:
Dmitriy Chubinidze
2025-11-23 22:49:15 +00:00
parent b62ce91a0f
commit 0046d1a203
1 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
doc/source/admin/troubleshooting.rst
View File

@@ -49,7 +49,8 @@ Perform the following checks:
on physical switches (if applicable)
- Check that hosts are in the same IP subnet
or have proper routing between them
- Check there are no iptables applied to the hosts that would deny traffic
- Check there are no firewall (firewalld, ufw, etc.) rules applied to the hosts
that would deny traffic
IP addresses should be applied to physical interface, bond interface,
tagged sub-interface, or in some cases the bridge interface:
@@ -75,7 +76,8 @@ Perform the following checks:
- Check VLAN configurations and any necessary trunking to uplink ports
on physical switches (if applicable)
- Check that hosts are in the same subnet or have proper routing between them
- Check there are no iptables applied to the hosts that would deny traffic
- Check there are no firewall (firewalld, ufw, etc.) rules applied to the hosts
that would deny traffic
- Check to verify that physical interface is in the bridge
- Check to verify that veth-pair end from container is in ``br-mgmt``
@@ -138,7 +140,8 @@ Perform the following checks:
- Check VLAN configurations and any necessary trunking to uplink ports
on physical switches (if applicable)
- Check that hosts are in the same subnet or have proper routing between them
- Check there are no iptables applied to the hosts that would deny traffic
- Check there are no firewall (firewalld, ufw, etc.) rules applied to the hosts
that would deny traffic
- Check to verify that physcial interface is in the bridge
- Check to verify that veth-pair end from container is in ``br-vxlan``