[KNOX-2921] [Ozone-Knox] Port blocking on one OM Instance blocks all the OM UIs

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Assignee: Zita Dombi
• Reporter: Pratyush Bhatt
• Created: 11/Jun/23 04:47
• Updated: 25/Jul/23 12:57
• Resolved: 25/Jul/23 12:57

Description

ozone.om.https-port is set to 9875

Blocked the port on one of the OM instance:

[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

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.

Issue Links

• duplicates: KNOX-2930 Fix OM and SCM UIs to work in HA