different behaviour between upgrading to a local charm and to a charmstore charm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
Hi,
juju 2.4.5. Currently, an old nrpe-external-
If I download cs:nrpe locally, unzip it and try to upgrade-charm --switch to it, I have a failure message :
$ juju upgrade-charm --debug --switch /path/to/nrpe nrpe
[...]
github.
However, I can upgrade to cs:nrpe without problem :
$ juju upgrade-charm --debug --switch cs:nrpe nrpe
Added charm "cs:nrpe-52" to the model.
And then I can switch to the local version without problem either :
$ juju upgrade-charm --debug --switch /path/to/nrpe nrpe
Added charm "local:
What could be causing this ?
Thanks
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.5.1 |
Changed in juju: | |
milestone: | 2.5.1 → 2.5.2 |
Changed in juju: | |
milestone: | 2.5.2 → 2.5.3 |
Changed in juju: | |
milestone: | 2.5.3 → 2.5.4 |
Changed in juju: | |
milestone: | 2.5.4 → 2.5.5 |
Changed in juju: | |
milestone: | 2.5.6 → 2.5.8 |
Changed in juju: | |
milestone: | 2.5.8 → 2.5.9 |
Did the charm change name? I'm trying to see how it works after the upgrade-charm to the later store version and wonder if something in the metadata changed that allowed it to pass through. It looks like it's named "nrpe-external- master" but then you say it works after upgrade with just nrpe? Were these two different tests?
Thanks for the additional details on the different scenarios.