| Summary: | All ports seem to be blocked after ansible install | ||
|---|---|---|---|
| Product: | OKD | Reporter: | Dean Peterson <dean.peterson> |
| Component: | Networking | Assignee: | Eric Paris <eparis> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Meng Bo <bmeng> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.x | CC: | aos-bugs, eparis, jdetiber |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-02-23 16:42:41 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
the ansible scripts should have configured firewalld or iptables-services with additional information, but should not have broken things like ssh which were previously correctly configured. Can you show us your iptables rules not? iptables -nvL iptables -nvL -t nat systemctl status iptables systemctl status firewalld cat /etc/sysconfig/iptables Thank you! closing bz as this was filed twice. Either forum is ok, but both is inappropriate. https://github.com/openshift/origin/issues/7546 |
Description of problem: I performed an ansible install of openshift origin. If I am on the local machine, I can bring up openshift in the browser. However, on any external machine, I am no longer able to access anything on the openshift master. I am unable to ssh, or visit the openshift web console in a browser. I checked iptables and all of the necessary ports are open. I even stopped it. Firewalld is also not running. I was able to ssh prior to the ansible install but something during that install blocked all external traffic. How do I open things back up? When I uninstall openshift using the same playbook the network is restored. ip addr list: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000 link/ether bc:5f:f4:ca:49:a7 brd ff:ff:ff:ff:ff:ff inet 23.25.149.227/29 brd 23.25.149.231 scope global enp1s0f0 valid_lft forever preferred_lft forever inet6 2601:446:1:a00::dd14/128 scope global dynamic valid_lft 603499sec preferred_lft 603499sec inet6 2601:446:1:a00:be5f:f4ff:feca:49a7/64 scope global noprefixroute dynamic valid_lft 183782sec preferred_lft 183782sec inet6 fe80::be5f:f4ff:feca:49a7/64 scope link valid_lft forever preferred_lft forever 3: enp1s0f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000 link/ether bc:5f:f4:cb:a2:2b brd ff:ff:ff:ff:ff:ff 4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN link/ether 52:54:00:3f:16:1b brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN qlen 500 link/ether 52:54:00:3f:16:1b brd ff:ff:ff:ff:ff:ff 7: lbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP link/ether ea:60:65:20:6e:57 brd ff:ff:ff:ff:ff:ff inet 10.1.0.1/24 scope global lbr0 valid_lft forever preferred_lft forever inet6 fe80::b85d:61ff:fecc:39c3/64 scope link valid_lft forever preferred_lft forever 8: vovsbr@vlinuxbr: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc pfifo_fast master ovs-system state UP link/ether f2:b2:07:13:20:8a brd ff:ff:ff:ff:ff:ff inet6 fe80::f0b2:7ff:fe13:208a/64 scope link valid_lft forever preferred_lft forever 9: vlinuxbr@vovsbr: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc pfifo_fast master lbr0 state UP link/ether ea:60:65:20:6e:57 brd ff:ff:ff:ff:ff:ff inet6 fe80::e860:65ff:fe20:6e57/64 scope link valid_lft forever preferred_lft forever 10: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN link/ether 7e:03:7e:f5:fa:7d brd ff:ff:ff:ff:ff:ff 11: br0: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN link/ether 46:00:d8:3a:da:47 brd ff:ff:ff:ff:ff:ff 12: tun0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN link/ether ba:cb:ea:b4:fd:84 brd ff:ff:ff:ff:ff:ff inet 10.1.0.1/24 scope global tun0 valid_lft forever preferred_lft forever inet6 fe80::b8cb:eaff:feb4:fd84/64 scope link valid_lft forever preferred_lft forever ip route default via 23.25.149.230 dev enp1s0f0 proto static metric 100 10.1.0.0/16 dev tun0 proto kernel scope link 23.25.149.224/29 dev enp1s0f0 proto kernel scope link src 23.25.149.227 metric 100 172.30.0.0/16 dev tun0 scope link 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Simply running the ansible installer is the only step required 2. 3. Actual results: Expected results: Additional info: