[ 
https://issues.apache.org/jira/browse/HDDS-8805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pratyush Bhatt updated HDDS-8805:
---------------------------------
    Description: 
ozone.om.https-port is set to 9875

Blocked the port on one of the OM instance:
{noformat}
[root@ozn-kx4-3 ~]# sudo iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
[root@ozn-kx4-3 ~]# sudo iptables -A INPUT -p tcp --dport 9875 -j DROP
[root@ozn-kx4-3 ~]# sudo iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
DROP       tcp  --  anywhere             anywhere             tcp dpt:sapv1

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination{noformat}
The affected node UI is getting 500, which is correct, but along with that 
other two OM UI Instances are also throwing the same even when the port is not 
blocked there.

Test Cluster: https://ozn-kx4-1.ozn-kx4.root.hwx.site:7183/cmf/home

  was:
ozone.om.https-port is set to 9875

Blocked the port on one of the OM instance:
{noformat}
[root@ozn-kx4-3 ~]# sudo iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
[root@ozn-kx4-3 ~]# sudo iptables -A INPUT -p tcp --dport 9875 -j DROP
[root@ozn-kx4-3 ~]# sudo iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
DROP       tcp  --  anywhere             anywhere             tcp dpt:sapv1

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination{noformat}
The affected node UI is getting 500, which is correct, but along with that 
other two OM UI Instances are also throwing the same even when the port is not 
blocked there.


> [Ozone-Knox] Port blocking on one OM Instance blocks all the OM UIs
> -------------------------------------------------------------------
>
>                 Key: HDDS-8805
>                 URL: https://issues.apache.org/jira/browse/HDDS-8805
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: Ozone Manager
>            Reporter: Pratyush Bhatt
>            Priority: Major
>         Attachments: image (6).png, image (7).png, image (8).png
>
>
> ozone.om.https-port is set to 9875
> Blocked the port on one of the OM instance:
> {noformat}
> [root@ozn-kx4-3 ~]# sudo iptables -L
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
> [root@ozn-kx4-3 ~]# sudo iptables -A INPUT -p tcp --dport 9875 -j DROP
> [root@ozn-kx4-3 ~]# sudo iptables -L
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
> DROP       tcp  --  anywhere             anywhere             tcp dpt:sapv1
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination{noformat}
> The affected node UI is getting 500, which is correct, but along with that 
> other two OM UI Instances are also throwing the same even when the port is 
> not blocked there.
> Test Cluster: https://ozn-kx4-1.ozn-kx4.root.hwx.site:7183/cmf/home



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to