Red Hat Bugzilla – Bug 1268914
oadm router liveness wrong when a different port is specified
Last modified: 2015-10-21 02:59:08 EDT
Description of problem:
If you specify different ports for node and port (like --ports '80:8080') when you create a router with hostnetwork=false, the liveness probe is configured to query 8080, but it checks the pod IP, so it fails because it should check the port 80.
Modifying the dc to set the liveness probe to query port 80 works, but I think it should be done by default.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. As per description
This turned out to be a confusion between host ports and container ports, not a bug.