Bug 1268914 - oadm router liveness wrong when a different port is specified
Summary: oadm router liveness wrong when a different port is specified
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Ram Ranganathan
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-05 15:24 UTC by Miheer Salunke
Modified: 2022-08-04 22:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-21 06:59:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Miheer Salunke 2015-10-05 15:24:08 UTC
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):
3.0

How reproducible:
Always

Steps to Reproduce:
1. As per description
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Josep 'Pep' Turro Mauri 2015-10-21 06:59:08 UTC
This turned out to be a confusion between host ports and container ports, not a bug.


Note You need to log in before you can comment on or make changes to this bug.