Comment 2 for bug 1924677

I was able to 'juju deploy snappass-test' today and it very quickly
deployed and did not have these messages in the logs.
However, it sounds like this is a problem more for the
delete/deploy/delete/deploy cycle.

Doing a remove-application followed by another deploy, I did see:

controller-0: 11:37:48 WARNING juju.apiserver.caasapplicationprovisioner
ignoring non-existent unit with provider id "snappass-test-0"

But nothing otherwise worrying.

Trying 'juju destroy-model test; juju add-model test2' and then doing
another deploy:

Each test didn't give an error, and each test showed snappass-test running
in significantly under 1min (mostly in the few seconds range).

On Tue, Apr 20, 2021 at 6:55 PM John A Meinel <email address hidden>
wrote:

> ** Changed in: juju
> Milestone: 2.9-rc11 => 2.9.1
>
> ** Changed in: juju
> Importance: Undecided => High
>
> ** Changed in: juju
> Status: Incomplete => Triaged
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1924677
>
> Title:
> Glitch with K8s sidecar deploy: remote charm modified version does not
> match agent's
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1924677/+subscriptions
>