Bug 1324548

Summary: GCE Load balancer not created with service type loadbalancer
Product: OpenShift Container Platform Reporter: jawed <jkhelil>
Component: NodeAssignee: Seth Jennings <sjenning>
Status: CLOSED NOTABUG QA Contact: DeShuai Ma <dma>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.1.0CC: agoldste, aos-bugs, ccoleman, jokerman, mmccomas
Target Milestone: ---Keywords: UpcomingRelease
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-07 09:16:20 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:

Description jawed 2016-04-06 15:19:15 UTC
Description of problem:
Load balancer not created on gce

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


How reproducible:


Steps to Reproduce:
1. create ose cluster on gce (with openshift-ansible byo mode passing the cloud-provider args)
2. edit restricted scc to change RunAsUser as  RunAsAny
2. create pod oc run nginx --image=gcr.io/google_containers/nginx 
3. create service with oc create -f service.yml
with service.yml
apiVersion: v1
kind: Service
metadata:
  name: nginxservice
  labels:
    run: nginx
spec:
  ports:
  - port: 80
    targetPort: 80
    protocol: TCP
  selector:
    run: nginx
  type: LoadBalancer


Actual results:

Load balancer not created, no target pool, no forwarding rule, no lb

Expected results:
target pool created on gce
forwarding rule created on gce 
gce LB created

Additional info:
Putting debeug level 6 at master and node but nothing in logs related to service loadbalancer

Comment 1 Andy Goldstein 2016-04-06 21:02:14 UTC
The ServiceController is not currently enabled in either Origin or OSE; therefore, cloud services such as load balancers are not supported.

Comment 2 jawed 2016-04-07 06:24:08 UTC
Ok thank you Andy, That's explain all

Comment 3 jawed 2016-04-07 06:27:29 UTC
Does it mean that it is a beta feature for the 3.1 and will be enabled for 3.2 or does it mean that it can not be enabled in 3.1 at all ?

Comment 4 jawed 2016-04-07 09:15:25 UTC
I will close this as it is not a bug

Comment 5 Andy Goldstein 2016-04-07 15:41:12 UTC
Not enabled in any 3.x release yet.