Bug 1323115 - Error 'the router is not selecting this route' occurs when testing compatiability with latest oc VS old openshift (v3.1.1.6.4)
Summary: Error 'the router is not selecting this route' occurs when testing compatiabi...
Keywords:
Status: CLOSED EOL
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Maciej Szulik
QA Contact: Wei Sun
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-01 10:18 UTC by Xingxing Xia
Modified: 2019-08-21 08:39 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-21 08:39:46 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Xingxing Xia 2016-04-01 10:18:03 UTC
Description of problem:
After creating route, oc status shows error 'the router is not selecting this route' when using latest oc VS old openshift.

Version-Release number of selected component (if applicable):
Server:
openshift v3.1.1.6-33-g81eabcc
kubernetes v1.1.0-origin-1107-g4c8e6f4
etcd 2.1.2

Client:
oc v3.2.0.9
kubernetes v1.2.0-36-g4a3f9c5

Image:
haproxy-router    v3.1.1.6            b4802aef71cd        10 hours ago        456.8 MB

How reproducible:
Always

Steps to Reproduce:
1. On client host (oc v3.2.0.9), oc login, create new project xxia-proj
2. Create route:
$ oc new-app openshift/hello-openshift --name app
$ oc expose svc app
3. 
$ oc get pod -n default --config=</path/to/admin.kubeconfig>
router-1-y3k3w            1/1       Running   0          51m
$ oc status -n xxia-proj

Actual results:
3.
Errors:
  * route/app is routing traffic to svc/app, but either the administrator has not installed a router or the router is not selecting this route.

Expected results:
3. The error should not occur

Additional info:
When checking oc 3.1.1.6-33 VS openshift 3.1.1.6-33 and oc 3.2.0.9 VS openshift 3.2.0.9, the error does not occur. So this is a compatiability issue.

Comment 1 Clayton Coleman 2016-04-01 16:41:24 UTC
The status warning should only show up if the ingress field has been populated by the server.  The warning is too specific.

Comment 2 Maciej Szulik 2019-08-21 08:39:46 UTC
Closing due to age.


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