[KNOX-2917] [Ozone-Knox] Port blocking on one SCM Instance blocks all the SCM UI Nodes

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

Description

ozone.scm.https-port is set as 9877

Blocked the port on one of the SCM 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 9877 -j DROP
[root@ozn-kx4-3 ~]# sudo iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
DROP       tcp  --  anywhere             anywhere             tcp dpt:9877

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

The affected node is getting 500, which is correct, but along with that other two SCM 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