Comment 2 for bug 1838780

Revision history for this message
Chris Sanders (chris.sanders) wrote :

Poking around in the database some more I found a server certificate, which I assumed is from the old server. I pulled the one off the new server x.x.x.107 and poked it into mongo with:

db.cloudCredentials.updateOne({"_id":"prod-lxd#admin#prod-lxd-creds"},{$set: {"attributes.server-cert" : "server.cert here" }})

Now the error message when I get when trying to ssh to a unite is:

ERROR opening environment: Get https://192.168.0.107:8443/1.0: x509: certificate is valid for 192.168.0.226, not 192.168.0.107

I think I'm closer, but this is madness for what should be an expected failure mode for a cluster. I guess I'll do some more database splunking to see if I can figure out what's going on. Any advice or documentation I'm missing available by chance?