node --boostrap fails

[debianmaster]

i'm trying to use the new node bootstrap feature to bootstrap a new node.

Step 1: started all in one server on node1
Step 2: copied admin.kubeconfig to node2
Step 3: tried to bootstrap using --bootstrap=true --kubeconfig=admin.kubeconfig

Bootstrap faile with timeout, more details in the last section

Version

oc v3.6.0-alpha.0+0343989
8d-0eda-11e7-b63a-42010a800003").
kubernetes v1.5.2+43a9be4

Steps To Reproduce

node1: 146.148.85.109 (internal ip 10.128.0.3)
node2: 146.148.38.249

on node1:

./openshift start --public-master='https://146.148.85.109:443' --listen='https://0.0.0.0:443' --master='https://10.128.0.3:443'

copy admin.kubeconfig to node2

on node2

./openshift start node --bootstrap --kubeconfig=admin.kubecofnig  --loglevel=6

Current Result

I0322 08:39:36.752063    2374 round_trippers.go:318] GET https://10.128.0.3:443/apis/certificates.k8s.io/v1alpha1/certificatesigningrequests/node-bootstrapper-client-ocp-cluster-p0vr 200 OK in 2 milliseconds
I0322 08:39:37.752309    2374 round_trippers.go:318] GET https://10.128.0.3:443/apis/certificates.k8s.io/v1alpha1/certificatesigningrequests/node-bootstrapper-client-ocp-cluster-p0vr 200 OK in 2 milliseconds
I0322 08:39:37.754002    2374 round_trippers.go:318] GET https://10.128.0.3:443/apis/certificates.k8s.io/v1alpha1/certificatesigningrequests/node-bootstrapper-client-ocp-cluster-p0vr 200 OK in 1 milliseconds
F0322 08:39:37.754139    2374 start_node.go:139] timed out waiting for the condition

Expected Result

node 2 should join openshift cluster as new node

Additional Information

[Note] Summary of diagnostics execution (version v3.6.0-alpha.0+0343989):
[Note] Warnings seen: 4

[smarterclayton]

You have to approve the certificates created by the node.

$ oc get certificates
$ oadm certificate approve NAME

[debianmaster]

show no resource type "certificates"

[root@master1 ocp]# ./oc get certificates --all-namespaces=true                            
[root@node1 ocp]# ls openshift.local.config/node
the server doesn't have a resource type "certificates"  

i checked on node too but certs, i'm i missing anything?

[smarterclayton]

Ah, typo - "certificatesigningrequests"

…

On Fri, Mar 24, 2017 at 2:30 AM, Chakradhar Rao Jonagam < ***@***.***> wrote: no certificates created on master ***@***.*** ocp]# ./oc get certificates --all-namespaces=true ***@***.*** ocp]# ls openshift.local.config/node the server doesn't have a resource type "certificates" i checked on node too but certs, i'm i missing anything? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#13500 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABG_pzJijgj3b-D-i8MutvJMK1KpQIioks5ro2MfgaJpZM4Mk4y_> .

[debianmaster]

New node logs after i did

./openshift start node --bootstrap --kubeconfig=admin.kubeconfig  --loglevel=6

I0327 00:36:17.176397    1625 bootstrap_node.go:115] Bootstrap client cert approved
F0327 00:36:17.176660    1625 start_node.go:139] bootstrap client certificate does not match private key, you may need to delete the client CSR: tls: failed to find any PEM data in certificate input

i have supplied admin.kubeconfig of master configuration, is it not right?

[debianmaster]

@smarterclayton any input pls.

[JacksonTech]

I have the same issue. Interestingly, the master-client.crt file in openshift.local.config/node is blank. Could this be the issue?

[debianmaster]

@JacksonTech i used admin.kubeconfig no luck , this really needs documentation on how to use

[JacksonTech]

@debianmaster tell you what, if we get it working, I will document it. I have a love for documentation!

[debianmaster]

@JacksonTech sure thing, i'll let you know when i get lucky with this

[debianmaster]

@smarterclayton any input on the error? or README

[smarterclayton]

You would need to delete the empty file in that case.

…

On Thu, Apr 6, 2017 at 8:17 PM, Chakradhar Rao Jonagam < ***@***.***> wrote: @smarterclayton <https://github.com/smarterclayton> any input on the error? or README — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#13500 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABG_pwMA8eMVwH0z8vGsFEc_8pC7_6Oeks5rtSwrgaJpZM4Mk4y_> .