[Bug 1315472] New: kube-controller-manager ignores --master argument

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1315472

            Bug ID: 1315472
           Summary: kube-controller-manager ignores --master argument
           Product: Fedora
           Version: 23
         Component: kubernetes
          Assignee: jchaloup(a)redhat.com
          Reporter: dustymabe(a)redhat.com
        QA Contact: extras-qa(a)fedoraproject.org
                CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org,
                    jcajka(a)redhat.com, jchaloup(a)redhat.com,
                    nhorman(a)redhat.com, vbatts(a)redhat.com



Description of problem:

kube-controller-manager ignores --master argument


Version-Release number of selected component (if applicable):
[root@f23 kubernetes]# rpm -qa | grep kubernetes sort
kubernetes-1.2.0-0.13.alpha6.gitf0cd09a.fc23.x86_64
kubernetes-client-1.2.0-0.13.alpha6.gitf0cd09a.fc23.x86_64
kubernetes-master-1.2.0-0.13.alpha6.gitf0cd09a.fc23.x86_64
kubernetes-node-1.2.0-0.13.alpha6.gitf0cd09a.fc23.x86_64

How reproducible:
Always

Steps to Reproduce:
After setting up system like you normally would do (create cert etc..) observe
the kube-controller manager service ignores the '--master' arg on the command
line.
You can repro with this command:
```
/usr/bin/kube-controller-manager --logtostderr=true --v=0
--master=http://127.0.0.1:8080
--service_account_private_key_file=/etc/pki/kube-apiserver/serviceaccount.key
```

I set up my systems using the lines in this ansible playbook: 
https://github.com/dustymabe/vagrantdirs/blob/master/f23/playbook.yml#L62


Actual results:

The following is the message you receive. Note the "nor --master was specified"
log message, which indicates it didn't recognize the
--master=http://127.0.0.1:8080 argument we provided: 

```
[root@f23 kubernetes]# /usr/bin/kube-controller-manager --logtostderr=true
--v=0 --master=http://127.0.0.1:8080
--service_account_private_key_file=/etc/pki/kube-apiserver/serviceaccount.key 
W0307 20:07:44.007893   13698 client_config.go:352] Neither --kubeconfig nor
--master was specified.  Using the inClusterConfig.  This might not work.
W0307 20:07:44.008076   13698 client_config.go:357] error creating
inClusterConfig, falling back to default config: %vunable to load in-cluster
configuration, KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT must be
defined
I0307 20:07:44.008618   13698 plugins.go:71] No cloud provider specified.
I0307 20:07:44.010789   13698 replication_controller.go:185] Starting RC
Manager
I0307 20:07:44.012329   13698 nodecontroller.go:134] Sending events to api
server.
E0307 20:07:44.012490   13698 controllermanager.go:212] Failed to start service
controller: ServiceController should not be run without a cloudprovider.
I0307 20:07:44.012519   13698 controllermanager.go:225] allocate-node-cidrs set
to false, node controller not creating routes
I0307 20:07:44.023177   13698 controllermanager.go:258] Starting
extensions/v1beta1 apis
I0307 20:07:44.023323   13698 controllermanager.go:260] Starting horizontal pod
controller.
I0307 20:07:44.023500   13698 controllermanager.go:274] Starting daemon set
controller
I0307 20:07:44.023730   13698 controllermanager.go:280] Starting job controller
I0307 20:07:44.023833   13698 controller.go:180] Starting Daemon Sets
controller manager
```

As a result we see this when trying to create a pod:

```
[root@f23 ~]# kubectl create -f /tmp/busybox.yaml 
Error from server: error when creating "/tmp/busybox.yaml": pods
"busybox" is
forbidden: no API token found for service account default/default, retry after
the token is automatically created and added to the service account
```

-- 
You are receiving this mail because:
You are on the CC list for the bug.