Yesterday I upgraded my working (canonistack lcy01) test environment to 1.25.6. All seemed to be well, with clean status and a quiet juju debug-log. I left it overnight without making any changes, and this morning all but two units are in agent lost state: https://pastebin.canonical.com/161942/
I'm not sure whether this is part of this same bug, or whether a new one should be created to address this specific situation, but to my mind if a working juju env can turn into a non-working juju env overnight with no changes being made, that should be considered a critical bug.
Yesterday I upgraded my working (canonistack lcy01) test environment to 1.25.6. All seemed to be well, with clean status and a quiet juju debug-log. I left it overnight without making any changes, and this morning all but two units are in agent lost state: https:/ /pastebin. canonical. com/161942/
I'm not sure whether this is part of this same bug, or whether a new one should be created to address this specific situation, but to my mind if a working juju env can turn into a non-working juju env overnight with no changes being made, that should be considered a critical bug.
I've just uploaded new logs from this environment to https:/ /private- fileshare. canonical. com/~paulgear/ lp:1513667/ - named juju-logs-*.tar.xz.