| 2017-08-15 14:06:13 |
José Pekkarinen |
bug |
|
|
added bug |
| 2017-08-15 14:06:35 |
José Pekkarinen |
description |
Hi,
On an environment were juju HA was 2.1.2 version, executing an upgrade to juju 2.1.3,
rendered on the secondary nodes not being able to connect to local mongodb:
2017-08-15 13:58:13 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:14 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:15 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:16 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:17 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:18 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:18 DEBUG juju.worker.dependency engine.go:500 "state" manifold worker stopped: cannot connect to mongodb: no reachable servers
2017-08-15 13:58:18 ERROR juju.worker.dependency engine.go:547 "state" manifold worker returned unexpected error: cannot connect to mongodb: no reachable servers
2017-08-15 13:58:21 DEBUG juju.cmd.jujud machine.go:1402 mongo is already initialized
2017-08-15 13:58:21 INFO juju.state open.go:121 opening state, mongo addresses: ["localhost:37017"]; entity machine-5
Reading the certificate, I can see:
# openssl x509 -text -noout -in /var/lib/juju/server.pem
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
1e:29:a6:06:22:87:cf:1f:4b:e8:80:8e:a8:bb:22:03:c4:3e:be
Signature Algorithm: sha256WithRSAEncryption
Issuer: O=juju, CN=juju-generated CA for model "juju-ca"/serialNumber=<valid-uuid>
Validity
...
X509v3 Subject Alternative Name:
DNS:juju-mongodb, DNS:local, DNS:juju-apiserver
...
Then the api-server won't start:
# lsof -i | grep LISTEN
sshd 4541 root 3u IPv4 44323 0t0 TCP *:ssh (LISTEN)
mongod 33430 root 6u IPv4 123993 0t0 TCP *:37017 (LISTEN)
And juju status won't notice about it:
$ juju status -m controller
Model Controller Cloud/Region Version
controller mycontroller myregion 2.1.3.1
App Version Status Scale Charm Store Rev OS Notes
Unit Workload Agent Machine Public address Ports Message
Machine State DNS Inst id Series AZ
0 started <valid-ip-address> <maas.machine.name> xenial AZ1
5 started <valid-ip-address> <maas.machine.name> xenial AZ2
9 started <valid-ip-address> <maas.machine.name> xenial AZ3
This is addressed in the following PR:
https://github.com/juju/juju/pull/7748
Thanks!
José. |
Hi,
On an environment were juju HA was 2.1.2 version, executing an upgrade to juju 2.1.3, rendered on the secondary nodes not being able to connect to local mongodb:
2017-08-15 13:58:13 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:14 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:15 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:16 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:17 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:18 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:18 DEBUG juju.worker.dependency engine.go:500 "state" manifold worker stopped: cannot connect to mongodb: no reachable servers
2017-08-15 13:58:18 ERROR juju.worker.dependency engine.go:547 "state" manifold worker returned unexpected error: cannot connect to mongodb: no reachable servers
2017-08-15 13:58:21 DEBUG juju.cmd.jujud machine.go:1402 mongo is already initialized
2017-08-15 13:58:21 INFO juju.state open.go:121 opening state, mongo addresses: ["localhost:37017"]; entity machine-5
Reading the certificate, I can see:
# openssl x509 -text -noout -in /var/lib/juju/server.pem
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
1e:29:a6:06:22:87:cf:1f:4b:e8:80:8e:a8:bb:22:03:c4:3e:be
Signature Algorithm: sha256WithRSAEncryption
Issuer: O=juju, CN=juju-generated CA for model "juju-ca"/serialNumber=<valid-uuid>
Validity
...
X509v3 Subject Alternative Name:
DNS:juju-mongodb, DNS:local, DNS:juju-apiserver
...
Then the api-server won't start:
# lsof -i | grep LISTEN
sshd 4541 root 3u IPv4 44323 0t0 TCP *:ssh (LISTEN)
mongod 33430 root 6u IPv4 123993 0t0 TCP *:37017 (LISTEN)
And juju status won't notice about it:
$ juju status -m controller
Model Controller Cloud/Region Version
controller mycontroller myregion 2.1.3.1
App Version Status Scale Charm Store Rev OS Notes
Unit Workload Agent Machine Public address Ports Message
Machine State DNS Inst id Series AZ
0 started <valid-ip-address> <maas.machine.name> xenial AZ1
5 started <valid-ip-address> <maas.machine.name> xenial AZ2
9 started <valid-ip-address> <maas.machine.name> xenial AZ3
This is addressed in the following PR:
https://github.com/juju/juju/pull/7748
Thanks!
José. |
|
| 2017-08-16 04:21:35 |
John A Meinel |
affects |
juju-core |
juju |
|
| 2017-08-16 04:21:35 |
John A Meinel |
juju: importance |
Undecided |
High |
|
| 2017-08-16 04:21:35 |
John A Meinel |
juju: status |
New |
Triaged |
|
| 2017-08-16 04:21:44 |
John A Meinel |
nominated for series |
|
juju/2.2 |
|
| 2017-08-16 04:21:44 |
John A Meinel |
bug task added |
|
juju/2.2 |
|
| 2017-08-16 04:21:50 |
John A Meinel |
juju/2.2: status |
New |
Triaged |
|
| 2017-08-16 04:21:52 |
John A Meinel |
juju/2.2: importance |
Undecided |
High |
|
| 2017-08-16 04:21:55 |
John A Meinel |
juju/2.2: milestone |
|
2.2.3 |
|
| 2017-08-16 04:22:11 |
John A Meinel |
juju/2.2: assignee |
|
José Pekkarinen (koalinux) |
|
| 2017-08-16 04:22:15 |
John A Meinel |
juju: milestone |
|
2.3-alpha1 |
|
| 2017-08-16 04:22:30 |
John A Meinel |
juju: assignee |
|
José Pekkarinen (jose-pekkarinen) |
|
| 2017-08-18 14:45:23 |
José Pekkarinen |
description |
Hi,
On an environment were juju HA was 2.1.2 version, executing an upgrade to juju 2.1.3, rendered on the secondary nodes not being able to connect to local mongodb:
2017-08-15 13:58:13 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:14 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:15 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:16 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:17 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:18 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:18 DEBUG juju.worker.dependency engine.go:500 "state" manifold worker stopped: cannot connect to mongodb: no reachable servers
2017-08-15 13:58:18 ERROR juju.worker.dependency engine.go:547 "state" manifold worker returned unexpected error: cannot connect to mongodb: no reachable servers
2017-08-15 13:58:21 DEBUG juju.cmd.jujud machine.go:1402 mongo is already initialized
2017-08-15 13:58:21 INFO juju.state open.go:121 opening state, mongo addresses: ["localhost:37017"]; entity machine-5
Reading the certificate, I can see:
# openssl x509 -text -noout -in /var/lib/juju/server.pem
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
1e:29:a6:06:22:87:cf:1f:4b:e8:80:8e:a8:bb:22:03:c4:3e:be
Signature Algorithm: sha256WithRSAEncryption
Issuer: O=juju, CN=juju-generated CA for model "juju-ca"/serialNumber=<valid-uuid>
Validity
...
X509v3 Subject Alternative Name:
DNS:juju-mongodb, DNS:local, DNS:juju-apiserver
...
Then the api-server won't start:
# lsof -i | grep LISTEN
sshd 4541 root 3u IPv4 44323 0t0 TCP *:ssh (LISTEN)
mongod 33430 root 6u IPv4 123993 0t0 TCP *:37017 (LISTEN)
And juju status won't notice about it:
$ juju status -m controller
Model Controller Cloud/Region Version
controller mycontroller myregion 2.1.3.1
App Version Status Scale Charm Store Rev OS Notes
Unit Workload Agent Machine Public address Ports Message
Machine State DNS Inst id Series AZ
0 started <valid-ip-address> <maas.machine.name> xenial AZ1
5 started <valid-ip-address> <maas.machine.name> xenial AZ2
9 started <valid-ip-address> <maas.machine.name> xenial AZ3
This is addressed in the following PR:
https://github.com/juju/juju/pull/7748
Thanks!
José. |
Hi,
On an environment were juju HA was 2.1.2 version, executing an upgrade to juju 2.1.3, rendered on the secondary nodes not being able to connect to local mongodb:
2017-08-15 13:58:13 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:14 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:15 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:16 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:17 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:18 DEBUG juju.mongo open.go:144 dialled mongodb server at "127.0.0.1:37017"
2017-08-15 13:58:18 DEBUG juju.worker.dependency engine.go:500 "state" manifold worker stopped: cannot connect to mongodb: no reachable servers
2017-08-15 13:58:18 ERROR juju.worker.dependency engine.go:547 "state" manifold worker returned unexpected error: cannot connect to mongodb: no reachable servers
2017-08-15 13:58:21 DEBUG juju.cmd.jujud machine.go:1402 mongo is already initialized
2017-08-15 13:58:21 INFO juju.state open.go:121 opening state, mongo addresses: ["localhost:37017"]; entity machine-5
Reading the certificate, I can see:
# openssl x509 -text -noout -in /var/lib/juju/server.pem
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
1e:29:a6:06:22:87:cf:1f:4b:e8:80:8e:a8:bb:22:03:c4:3e:be
Signature Algorithm: sha256WithRSAEncryption
Issuer: O=juju, CN=juju-generated CA for model "juju-ca"/serialNumber=<valid-uuid>
Validity
...
X509v3 Subject Alternative Name:
DNS:juju-mongodb, DNS:local, DNS:juju-apiserver
...
Then the api-server won't start:
# lsof -i | grep LISTEN
sshd 4541 root 3u IPv4 44323 0t0 TCP *:ssh (LISTEN)
mongod 33430 root 6u IPv4 123993 0t0 TCP *:37017 (LISTEN)
And juju status won't notice about it:
$ juju status -m controller
Model Controller Cloud/Region Version
controller mycontroller myregion 2.1.3.1
App Version Status Scale Charm Store Rev OS Notes
Unit Workload Agent Machine Public address Ports Message
Machine State DNS Inst id Series AZ
0 started <valid-ip-address> <maas.machine.name> xenial AZ1
5 started <valid-ip-address> <maas.machine.name> xenial AZ2
9 started <valid-ip-address> <maas.machine.name> xenial AZ3
This is addressed in the following PR:
https://github.com/juju/juju/pull/7748
PR against 2.2:
https://github.com/juju/juju/pull/7755
Thanks!
José. |
|
| 2017-08-21 08:04:33 |
Paolo de Rosa |
tags |
|
4010 |
|
| 2017-09-06 22:33:54 |
Tim Penhey |
juju/2.2: status |
Triaged |
Fix Committed |
|
| 2017-09-08 01:39:23 |
Canonical Juju QA Bot |
juju/2.2: status |
Fix Committed |
Fix Released |
|
| 2017-09-27 11:52:54 |
Ante Karamatić |
tags |
4010 |
4010 cpe-onsite |
|
| 2017-10-05 21:05:53 |
Canonical Juju QA Bot |
juju: milestone |
2.3-beta1 |
2.3-beta2 |
|
| 2017-10-05 23:01:06 |
Anastasia |
juju: status |
Triaged |
Fix Committed |
|
| 2017-10-06 00:18:22 |
Anastasia |
juju: milestone |
2.3-beta2 |
2.3-beta1 |
|
| 2017-12-18 22:37:03 |
Anastasia |
juju: status |
Fix Committed |
Fix Released |
|
