Agent lost: invalid entity name or password (unauthorized access)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
While looking for reproducers for lp:1953077, I found a "lost" agent without the issue with previously failed actions mentioned there.
Its last logs were several weeks old:
2021-11-18 23:30:52 INFO juju.worker.
2021-11-18 23:30:53 ERROR juju.worker.
2021-11-18 23:30:53 ERROR juju.worker.
2021-11-18 23:30:53 INFO juju.worker.logger logger.go:136 logger worker stopped
2021-11-18 23:30:53 ERROR juju.worker.
2021-11-18 23:30:53 ERROR juju.worker.
2021-11-18 23:30:53 ERROR juju.worker.
2021-11-18 23:30:53 INFO juju.worker.uniter uniter.go:323 unit "myapp-wsgi/3" shutting down: catacomb 0xc000ee4d80 is dying
2021-11-18 23:30:53 ERROR juju.worker.
2021-11-18 23:30:53 ERROR juju.worker.
2021-11-18 23:40:13 INFO juju unit_agent.go:253 Starting unit workers for "myapp-wsgi/3"
2021-11-18 23:40:13 INFO juju.agent.setup agentconf.go:128 setting logging config to "<root>
2021-11-18 23:40:13 INFO juju.worker.
2021-11-18 23:40:54 ERROR juju.worker.
Restarting the jujud didn't generate any new log lines for this unit (it did for all the others on the same machine).
This is on juju 2.9.21, on an openstack cloud.
``` dependency engine.go:676 "meter-status" manifold worker returned unexpected error: watcher has been stopped (stopped)
2021-11-18 23:30:53 ERROR juju.worker.
2021-11-18 23:30:53 INFO juju.worker.uniter uniter.go:323 unit "myapp-wsgi/3" shutting down: catacomb 0xc000ee4d80 is dying
```
Feels like there should be some corresponding logs on the controller side from around this same time period which might give us a clue as to why it is stopping the watcher and closing the connection.