Sidecar charm get stuck if PodSpec charm with same name was deployed previously

[Dominik Fleischmann]

If you deploy a sidecar charm in a model where you deployed a pod spec charm with the same name the sidecar charm will get stuck in the "allocating" "installing agent" stage. Nothing will show up in the status log.

Steps to reproduce:

juju add-model test
juju deploy cs:kubeflow-volumes

git clone https://github.com/canonical/kubeflow-volumes-operator.git
cd kubeflow-volumes-operator
git checkout sidecar
charmcraft build

juju remove-application kubeflow-volumes
# Wait for application to be removed

juju deploy ./kubeflow-volumes_ubuntu-20.04-amd64.charm --resource kf-volumes-image=public.ecr.aws/j1r0q0g6/notebooks/volumes-web-app:v1.3.0-rc.1
# Application will get stuck

[John A Meinel (jameinel)]

I know Ben recently did some work to address being able to upgrade from a
pod-spec charm to a sidecar charm. I wonder if some of this might be
addressed in juju 2.9.10. It is interesting that the issue is actually for
an application that was otherwise completely removed, it sounds like the
removal left something problematic behind.

On Wed, Aug 4, 2021 at 10:15 AM Dominik Fleischmann <
<email address hidden>> wrote:

> Public bug reported:
>
> If you deploy a sidecar charm in a model where you deployed a pod spec
> charm with the same name the sidecar charm will get stuck in the
> "allocating" "installing agent" stage. Nothing will show up in the
> status log.
>
> Steps to reproduce:
>
> juju add-model test
> juju deploy cs:kubeflow-volumes
>
> git clone https://github.com/canonical/kubeflow-volumes-operator.git
> cd kubeflow-volumes-operator
> git checkout sidecar
> charmcraft build
>
> juju remove-application kubeflow-volumes
> # Wait for application to be removed
>
> juju deploy ./kubeflow-volumes_ubuntu-20.04-amd64.charm --resource
> kf-volumes-image=public.ecr.aws/j1r0q0g6/notebooks/volumes-web-app:v1.3.0-rc.1
> # Application will get stuck
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> ** Description changed:
>
> If you deploy a sidecar charm in a model where you deployed a pod spec
> charm with the same name the sidecar charm will get stuck in the
> "allocating" "installing agent" stage. Nothing will show up in the
> status log.
>
> Steps to reproduce:
>
> juju add-model test
> juju deploy cs:kubeflow-volumes
>
> git clone https://github.com/canonical/kubeflow-volumes-operator.git
> cd kubeflow-volumes-operator
> - git checkout sidecar
> + git checkout sidecar
> charmcraft build
>
> juju remove-application kubeflow-volumes
> # Wait for application to be removed
>
> juju deploy ./kubeflow-volumes_ubuntu-20.04-amd64.charm --resource
> kf-volumes-image=public.ecr.aws/j1r0q0g6/notebooks/volumes-web-app:v1.3.0-rc.1
> # Application will get stuck
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1938907
>
> Title:
> Sidecar charm get stuck if PodSpec charm with same name was deployed
> previously
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1938907/+subscriptions
>
>

[Dominik Fleischmann (dominik.f)]

Sorry I forgot to add the version, this was all tested in a fresh VM with juju 2.9.10.

[Yang Kelvin Liu (kelvin.liu)]

https://github.com/juju/juju/pull/13600