| 2018-12-10 16:39:54 |
Alexander Balderson |
bug |
|
|
added bug |
| 2018-12-10 16:39:54 |
Alexander Balderson |
attachment added |
|
machine-1.log https://bugs.launchpad.net/bugs/1807735/+attachment/5220915/+files/machine-1.log |
|
| 2018-12-10 20:02:46 |
Alexander Balderson |
attachment added |
|
juju-crashdump-controller-2018-12-07-14.23.12.tar.gz https://bugs.launchpad.net/juju/+bug/1807735/+attachment/5220938/+files/juju-crashdump-controller-2018-12-07-14.23.12.tar.gz |
|
| 2018-12-21 16:56:59 |
Chris Gregan |
attachment added |
|
logs-2018-12-21-14.30.03.tar https://bugs.launchpad.net/juju/+bug/1807735/+attachment/5224137/+files/logs-2018-12-21-14.30.03.tar |
|
| 2018-12-21 16:57:19 |
Chris Gregan |
attachment added |
|
juju-crashdump-controller-2018-12-21-14.30.49.tar.gz https://bugs.launchpad.net/juju/+bug/1807735/+attachment/5224138/+files/juju-crashdump-controller-2018-12-21-14.30.49.tar.gz |
|
| 2019-01-09 17:08:36 |
John George |
attachment added |
|
juju-crashdump-controller-2019-01-08-22.55.11.tar.gz https://bugs.launchpad.net/juju/+bug/1807735/+attachment/5228011/+files/juju-crashdump-controller-2019-01-08-22.55.11.tar.gz |
|
| 2019-01-14 12:47:27 |
Richard Harding |
juju: status |
New |
Triaged |
|
| 2019-01-14 12:47:29 |
Richard Harding |
juju: importance |
Undecided |
High |
|
| 2019-01-14 12:47:32 |
Richard Harding |
juju: milestone |
|
2.5.1 |
|
| 2019-01-23 07:16:19 |
Alexander Balderson |
bug |
|
|
added subscriber Canonical Field Critical |
| 2019-01-28 14:28:44 |
Vladimir Grevtsev |
bug |
|
|
added subscriber Vladimir Grevtsev |
| 2019-01-28 14:56:29 |
Richard Harding |
juju: importance |
High |
Critical |
|
| 2019-01-28 14:56:36 |
Richard Harding |
juju: assignee |
|
Tim Penhey (thumper) |
|
| 2019-01-28 16:01:58 |
Edward Hope-Morley |
tags |
|
sts |
|
| 2019-01-29 02:54:25 |
Tim Penhey |
juju: status |
Triaged |
In Progress |
|
| 2019-01-29 23:49:01 |
Dominique Poulain |
bug |
|
|
added subscriber Dominique Poulain |
| 2019-01-30 20:50:23 |
Tim Penhey |
juju: status |
In Progress |
Fix Committed |
|
| 2019-02-07 16:24:21 |
Alexander Balderson |
attachment added |
|
juju-crashdump-controller-2019-02-06-15.41.35.tar.gz https://bugs.launchpad.net/juju/+bug/1807735/+attachment/5236770/+files/juju-crashdump-controller-2019-02-06-15.41.35.tar.gz |
|
| 2019-02-07 21:36:56 |
Alexander Balderson |
tags |
sts |
cdo-qa sts |
|
| 2019-02-07 21:37:10 |
Alexander Balderson |
tags |
cdo-qa sts |
cdo-qa foundations-engine sts |
|
| 2019-02-08 01:07:58 |
Jason Hobbs |
description |
During bundle deployment, a juju controller became unable to connect to itself:
2018-12-07 14:10:26 ERROR juju.worker.dependency engine.go:632 "api-caller" manifold worker returned unexpected error: [cccf2a] "machine-1" cannot open api: unable to connect to API: dial tcp 127.0.0.1:17070: connect: connection refused
2018-12-07 14:10:30 WARNING juju.mongo open.go:160 mongodb connection failed, will retry: dial tcp 127.0.0.1:37017: connect: connection refused
2018-12-07 14:10:30 WARNING juju.mongo open.go:160 mongodb connection failed, will retry: dial tcp 10.244.40.236:37017: connect: connection refused
See attached machine log. |
During bundle deployment, a juju controller became unable to connect to itself:
2018-12-07 14:10:26 ERROR juju.worker.dependency engine.go:632 "api-caller" manifold worker returned unexpected error: [cccf2a] "machine-1" cannot open api: unable to connect to API: dial tcp 127.0.0.1:17070: connect: connection refused
2018-12-07 14:10:30 WARNING juju.mongo open.go:160 mongodb connection failed, will retry: dial tcp 127.0.0.1:37017: connect: connection refused
2018-12-07 14:10:30 WARNING juju.mongo open.go:160 mongodb connection failed, will retry: dial tcp 10.244.40.236:37017: connect: connection refused
See attached machine log.
Note - these errors/warnings don't necessarily indicate a problem. Only if they happen after a deploy starts:
01:01 < jhobbs> debug_log.txt:machine-2: 20:27:46 ERROR juju.worker.dependency "api-caller" manifold worker returned unexpected error: [1b66e5] "machine-2" cannot open api: unable to
connect to API: dial tcp 127.0.0.1:17070: connect: connection refused
01:01 < jhobbs> debug_log.txt:machine-2: 20:27:46 WARNING juju.mongo mongodb connection failed, will retry: dial tcp 127.0.0.1:37017: connect: connection refused
01:01 < jhobbs> debug_log.txt:machine-2: 20:27:46 WARNING juju.mongo mongodb connection failed, will retry: dial tcp 10.244.40.239:37017: connect: connection refused
01:01 < jhobbs> thumper: the controller logs exactly match the bug description; timeout is a secondary result of some other failure and I expect the triager suspected those errors/warnings.
Are those logs red herrings?
01:04 -!- kelvinliu [kelvinliu@58.168.67.220] has quit [The TLS connection was non-properly terminated.]
01:05 < thumper> jhobbs: yeah... those are expected
01:05 < thumper> those happened during enable-ha
01:05 < thumper> when you are adding mongo's to the replicaset, it drops all connections
01:05 < thumper> these would only be a problem if we see them after the deploy has started
01:06 < thumper> mongo can take up to two minutes to settle with a new replicaset |
|
| 2019-02-15 00:02:11 |
Canonical Juju QA Bot |
juju: status |
Fix Committed |
Fix Released |
|
