kubeedge: When I add an edge to cloud,error occurs and reports[fail to signCerts! error:unable to ParseECPrivateKey: x509: failed to parse private key (use ParsePKCS1PrivateKey instead for this key format)]
What happened: the edge is successfully join to the cloud by using “./keadm join --cloudcore-ipport=:10000 --token=” sentence,but error occurs when I use “edgecore” to add an edge end to the cloud end,error occurs and reports[fail to signCerts! error:unable to ParseECPrivateKey: x509: failed to parse private key (use ParsePKCS1PrivateKey instead for this key format)]
What you expected to happen: it could be added to the cloud and no error occurs
How to reproduce it (as minimally and precisely as possible):use./keadm join --cloudcore-ipport=<ip>:10000 --token=<token> to add the edge end while do not use keadm to create the cloud end
Anything else we need to know?:
Environment:
- KubeEdge version(e.g.
cloudcore/edgecore --version
): 1.3.1
CloudSide Environment:
- Hardware configuration (e.g.
lscpu
):1cpu 2gram - OS (e.g.
cat /etc/os-release
):Centos7 - Kernel (e.g.
uname -a
):Linux new 3.10.0-1062.1.2.el7.x86_64 #1 SMP Mon Sep 30 14:19:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux - Go version (e.g.
go version
): go1.14.1 linux/amd64 - Others:kubernates version:1.15.0
EdgeSide Environment:
- edgecore version (e.g.
edgecore --version
):1.3.1 - Hardware configuration (e.g.
lscpu
):1cpu 2gram - OS (e.g.
cat /etc/os-release
):Centos7 - Kernel (e.g.
uname -a
):Linux new 3.10.0-1062.1.2.el7.x86_64 #1 SMP Mon Sep 30 14:19:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux - Go version (e.g.
go version
): go version go1.14.1 linux/amd64 - Others:
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 17 (9 by maintainers)
thanks a lot,you are right,i start a new virtual machine and generate cloudcore without create these ca&cert directly run cloudcore,and then i successfully add an edgecore to the cloudcore
see https://github.com/kubeedge/kubeedge/issues/1714 I think you use x509 files generated in kubeedge-v1.2. you can try to remove /etc/kubeedge/ca and /etc/kubeedge/certs both cloud and edge side, delete all secreat in kubeedge ns of K8S. Then, restart cloudcore, configure edgecore’s token and restart edgecore