# Solution to Open Shift Cluster Running Issues ###### tags: `Acumos` , `Issues` ## Name : Christofel Rio Goenawan ## University : Bandung Institute of Technology (ITB) --- ## Issues First when Writer command the installation service for Acumos AI in NTUST server, the command asking for server name. The erro can be seen [here](https://hackmd.io/@christofel04/TEEP_Daily_Notes_05_8_2020). After checking the Open Shift cluster installation , there are issues when setting cluster up in Open Shift. The Open Shift cluster can be runned by command below. ``` oc cluster up``` :::danger In Writer's installation the setting freeze after installing kubeflow as below. ![](https://i.imgur.com/27U2fYv.png) But after look at [reference](https://github.com/openshift/origin/issues/21253) , it should end up showing Open Shift user account and server as below.. ![](https://i.imgur.com/WoHOBzT.png) ::: ## Solution In this solution Writer look at [documentation](https://github.com/openshift/origin/blob/release-3.11/docs/cluster_up_down.md#linux) where **for Open Shift cluster up in CentOS Version 7 and Open Shift Cluster 3.11 usually the firewall ID must be reconfigured first** . The reconfigured can be done by command in terminal as below. 1. First , check that ``net.ipv4.ip_forward`` parameter set to 1 ( ***activated*** ) in Server. The check can be done by command in terminal as below. ``` sysctl net.ipv4.ip_forward ``` 2. Then , add some ***Firewall ID*** policy as below. It need **sudo** command because it involved high policy in Server. ``` sudo firewall-cmd --permanent --new-zone dockerc sudo firewall-cmd --permanent --zone dockerc --add-source 172.17.0.0/16 sudo firewall-cmd --permanent --zone dockerc --add-port 8443/tcp sudo firewall-cmd --permanent --zone dockerc --add-port 53/udp sudo firewall-cmd --permanent --zone dockerc --add-port 8053/udp sudo firewall-cmd --reload ``` :::info If it still have same issues, try to find your own **Docker bridge network container subnet** by command below. ``` docker network inspect -f "{{range .IPAM.Config }}{{ .Subnet }}{{end}}" bridge ``` You should get a subnet like: ``172.17.0.0/16`` in my case. ::: The result is Open Shift Cluster Running as expected ![](https://i.imgur.com/nZOethm.png) Furthermore the command not asking server name anymore as below. ![](https://i.imgur.com/6zAMWcA.png)