Sidecar charm get stuck if PodSpec charm with same name was deployed previously
Bug #1938907 reported by
Dominik Fleischmann
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Yang Kelvin Liu |
Bug Description
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:/
cd kubeflow-
git checkout sidecar
charmcraft build
juju remove-application kubeflow-volumes
# Wait for application to be removed
juju deploy ./kubeflow-
# Application will get stuck
description: | updated |
Changed in juju: | |
milestone: | none → 2.9.11 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in juju: | |
milestone: | 2.9.11 → 2.9.12 |
Changed in juju: | |
milestone: | 2.9.12 → 2.9.13 |
Changed in juju: | |
milestone: | 2.9.13 → 2.9.14 |
Changed in juju: | |
milestone: | 2.9.14 → 2.9.15 |
Changed in juju: | |
milestone: | 2.9.15 → 2.9.16 |
Changed in juju: | |
milestone: | 2.9.16 → 2.9.17 |
Changed in juju: | |
milestone: | 2.9.17 → 2.9.18 |
Changed in juju: | |
milestone: | 2.9.18 → 2.9.19 |
Changed in juju: | |
milestone: | 2.9.19 → 2.9.20 |
Changed in juju: | |
milestone: | 2.9.20 → 2.9.21 |
Changed in juju: | |
milestone: | 2.9.21 → 2.9.22 |
Changed in juju: | |
milestone: | 2.9.22 → 2.9.23 |
Changed in juju: | |
status: | Triaged → In Progress |
assignee: | nobody → Yang Kelvin Liu (kelvin.liu) |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
milestone: | 2.9.23 → 2.9.24 |
Changed in juju: | |
milestone: | 2.9.24 → 2.9.25 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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: /github. com/canonical/ kubeflow- volumes- operator. git volumes- operator volumes_ ubuntu- 20.04-amd64. charm --resource image=public. ecr.aws/ j1r0q0g6/ notebooks/ volumes- web-app: v1.3.0- rc.1 /github. com/canonical/ kubeflow- volumes- operator. git volumes- operator volumes_ ubuntu- 20.04-amd64. charm --resource image=public. ecr.aws/ j1r0q0g6/ notebooks/ volumes- web-app: v1.3.0- rc.1 /bugs.launchpad .net/bugs/ 1938907 /bugs.launchpad .net/juju/ +bug/1938907/ +subscriptions
>
> 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:/
> cd kubeflow-
> git checkout sidecar
> charmcraft build
>
> juju remove-application kubeflow-volumes
> # Wait for application to be removed
>
> juju deploy ./kubeflow-
> kf-volumes-
> # 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:/
> cd kubeflow-
> - git checkout sidecar
> + git checkout sidecar
> charmcraft build
>
> juju remove-application kubeflow-volumes
> # Wait for application to be removed
>
> juju deploy ./kubeflow-
> kf-volumes-
> # Application will get stuck
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> Sidecar charm get stuck if PodSpec charm with same name was deployed
> previously
>
> To manage notifications about this bug go to:
> https:/
>
>