Tuesday, April 30, 2024
 Popular · Latest · Hot · Upcoming
1
rated 0 times [  1] [ 0]  / answers: 1 / hits: 1566  / 2 Years ago, fri, november 11, 2022, 4:24:00

I bootstrapped the juju environment for maas. It was working fine but, my bootstrapped node formatted due to network boot. I then removed juju and deleted the environments directory and reinstalled juju but not it give error as below. Please help me I'm not able to resolve the issue.



2014-09-18 12:12:11 DEBUG juju.mongo open.go:101 TLS handshake failed: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "juju-generated CA for environment "maas"")
2014-09-18 12:12:11 DEBUG juju.mongo open.go:101 TLS handshake failed: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "juju-generated CA for environment "maas"")
2014-09-18 12:12:11 DEBUG juju.mongo open.go:101 TLS handshake failed: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "juju-generated CA for environment "maas"")
2014-09-18 12:12:12 DEBUG juju.mongo open.go:101 TLS handshake failed: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "juju-generated CA for environment "maas"")
2014-09-18 12:12:13 DEBUG juju.mongo open.go:101 TLS handshake failed: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "juju-generated CA for environment "maas"")
2014-09-18 12:12:13 DEBUG juju.mongo open.go:101 TLS handshake failed: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "juju-generated CA for environment "maas"")
2014-09-18 12:12:13 DEBUG juju.mongo open.go:101 TLS handshake failed: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "juju-generated CA for environment "maas"")
2014-09-18 12:12:14 DEBUG juju.mongo open.go:101 TLS handshake failed: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "juju-generated CA for environment "maas"")
2014-09-18 12:12:15 DEBUG juju.mongo open.go:101 TLS handshake failed: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "juju-generated CA for environment "maas"")
2014-09-18 12:12:15 DEBUG juju.mongo open.go:101 TLS handshake failed: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "juju-generated CA for environment "maas"")
2014-09-18 12:12:15 DEBUG juju.mongo open.go:101 TLS handshake failed: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "juju-generated CA for environment "maas"")
2014-09-18 12:12:16 DEBUG juju.mongo open.go:101 TLS handshake failed: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "juju-generated CA for environment "maas"")
2014-09-18 12:12:16 INFO juju.worker.peergrouper initiate.go:71 finished MaybeInitiateMongoServer
2014-09-18 12:12:16 ERROR juju.cmd supercommand.go:323 cannot initiate replica set: can't dial mongo to initiate replicaset: no reachable servers
ERROR bootstrap failed: subprocess encountered error code 1
Stopping instance...
Bootstrap failed, destroying environment
ERROR subprocess encountered error code 1

More From » ssh

 Answers
6

If you've deleted your $HOME/.juju/ directory, which contains all the SSH keys and certificates juju has generated, without also destroying your juju environment, you won't be able to access the environment from juju anymore, as the credentials and keys are lost.



What I'd recommend is to bootstrap a new environment on your MAAS, using correctly commissioned nodes (in "Ready" state). This way the nodes won't be set to PXE boot and will boot from the local disk instead (e.g. if you reboot them they won't get wiped out but will work as expected).


[#23172] Saturday, November 12, 2022, 1 Year  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
cupwire

Total Points: 365
Total Questions: 126
Total Answers: 125

Location: Malaysia
Member since Thu, Feb 16, 2023
1 Year ago
;