Bug 1290128

Summary: Routers creation failures depending on user kubeconfig
Product: OpenShift Container Platform Reporter: Federico Simoncelli <fsimonce>
Component: ocAssignee: Fabiano Franz <ffranz>
Status: CLOSED CURRENTRELEASE QA Contact: Wei Sun <wsun>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.1.0CC: aos-bugs, jforrest, jokerman, jvallejo, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-23 17:14:11 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:
Embargoed:

Description Federico Simoncelli 2015-12-09 17:23:03 UTC 
Description of problem:
It should be possible to create a router independently from the current context of oc.

How reproducible:
100%

Steps to Reproduce:

# oc project openshift-infra
# oadm router router \
  --credentials=/etc/origin/master/openshift-router.kubeconfig \
  --service-account=router
error: router could not be created; unable to validate service account,
       host ports are forbidden
# oadm router router \
  --credentials=/etc/origin/master/openshift-router.kubeconfig \
  --service-account=router \
  --host-network=false
error: router could not be created; unable to validate service account,
       host ports are forbidden

# oc project default
# oadm router router \
  --credentials=/etc/origin/master/openshift-router.kubeconfig \
  --service-account=router
(success)

Actual results:
The router creation depends on the current context (project).

Expected results:
It should be possible to create a router independently from the current context (project).
(More info in the upstream issue, see below).

Additional info:
This may be relevant for registry and ipfailover as well (and other?).

Upstream issue:

https://github.com/openshift/origin/issues/6248
Comment 1 Jessica Forrester 2016-01-05 15:02:41 UTC 
Upstream issue marked as a P3, moving to low severity
Comment 2 Juan Vallejo 2017-10-23 17:14:11 UTC 
Origin issue has been closed [1]. Please re-open if issue still exists / could still use improvement from current behavior.

1. https://github.com/openshift/origin/issues/6248#issuecomment-274395689