Application fails to connect to controller during install, connection reset by peer

Bug #1898576 reported by Alexander Balderson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Invalid
Low
Unassigned

Bug Description

There are instances of a subordinate application is failing to connect to the juju controller during install and shutting down:

$ cat unit-telegraf-18.log | grep ERROR
2020-10-03 16:16:31 ERROR juju.worker.dependency engine.go:671 "upgrader" manifold worker returned unexpected error: codec.ReadHeader error: error receiving message: read tcp 10.244.40.207:37098->10.244.40.114:17070: read: connection reset by peer
2020-10-03 16:16:31 DEBUG install ERROR codec.ReadHeader error: error receiving message: read tcp 10.244.40.207:37098->10.244.40.114:17070: read: connection reset by peer
2020-10-03 16:16:31 ERROR juju.worker.dependency engine.go:671 "proxy-config-updater" manifold worker returned unexpected error: codec.ReadHeader error: error receiving message: read tcp 10.244.40.207:37098->10.244.40.114:17070: read: connection reset by peer
2020-10-03 16:16:31 ERROR juju.worker.dependency engine.go:671 "api-address-updater" manifold worker returned unexpected error: codec.ReadHeader error: error receiving message: read tcp 10.244.40.207:37098->10.244.40.114:17070: read: connection reset by peer
2020-10-03 16:16:31 ERROR juju.worker.dependency engine.go:671 "migration-inactive-flag" manifold worker returned unexpected error: codec.ReadHeader error: error receiving message: read tcp 10.244.40.207:37098->10.244.40.114:17070: read: connection reset by peer
2020-10-03 16:16:31 ERROR juju.worker.dependency engine.go:671 "migration-minion" manifold worker returned unexpected error: codec.ReadHeader error: error receiving message: read tcp 10.244.40.207:37098->10.244.40.114:17070: read: connection reset by peer
2020-10-03 16:16:31 ERROR juju.worker.dependency engine.go:671 "api-caller" manifold worker returned unexpected error: codec.ReadHeader error: error receiving message: read tcp 10.244.40.207:37098->10.244.40.114:17070: read: connection reset by peer
2020-10-03 16:16:35 DEBUG install ERROR connection is shut down
2020-10-03 16:16:44 DEBUG install ERROR connection is shut down
2020-10-03 16:16:44 ERROR juju.worker.uniter.context context.go:1146 cannot apply changes: connection is shut down
2020-10-03 16:16:44 ERROR juju.worker.uniter.operation runhook.go:136 hook "install" (via explicit, bespoke hook script) failed: cannot apply changes: connection is shut down

It is a subordinate application relating to an application in one model for placement, and relaying information to a 2nd model by way of CMR.

Full logs can be found at:
https://solutions.qa.canonical.com/openstack/testRun/37647399-9f15-4c08-a99b-0e48004b89cb

Revision history for this message
Alexander Balderson (asbalderson) wrote :

All future test runs which hit this bug can be found at
https://solutions.qa.canonical.com/bugs/bugs/bug/1898576

Revision history for this message
Pen Gale (pengale) wrote :

Triaged as medium and dropped into 2.8.6 milestone. This looks like the sort of sporadic issue that we should fix so that our Solutions QA tests will run more consistently.

Changed in juju:
status: New → Triaged
importance: Undecided → Medium
milestone: none → 2.8.6
Pen Gale (pengale)
Changed in juju:
milestone: 2.8.6 → 2.8-next
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: Medium → Low
tags: added: expirebugs-bot
Revision history for this message
Konstantinos Kaskavelis (kaskavel) wrote :

Closing this due to inactivity (low number of occurrences, and no hit for more than one year)

tags: added: solutions-qa-expired
Changed in juju:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.