Comment 2 for bug 2057928

From the unit logs

2024-03-13 09:55:15 INFO juju unit_agent.go:289 Starting unit workers for "polkadot/0"
2024-03-13 09:55:15 ERROR juju.worker.apicaller connect.go:209 Failed to connect to controller: invalid entity name or password (unauthorized access)

We have seen this randomly in various scenarios and have not yet been able to isolate the cause. There would also be corresponding logs on the controller side with more info - not sure if those are available or not.

Ideally, we'd like to be able to reproduce this so we can diagnose further, but have not had much luck.

Can you provide some more detail on your set up:

- how was the controller configured; was it lxd on maas? can we get a juju status --format yaml?
- what was deployed to the model being migrated; can you share the bundle that was used
- for large models, we recommend tweaking the controller api request throttle params; was this done here?
- how often does the agent lost thing happen? One or several per model?
- what do the source and target controller logs show for the relevant period etc? Is it possible to set logging config on source and target controllers to include "#migration=DEBUG" so we can get extra logs if it fails?

If we can reproduce we can look at the logs ourselves etc.