Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

juju refresh to locally built charm does not work due to charm names being different #10

Open
sudeephb opened this issue Dec 7, 2023 · 0 comments

Comments

@sudeephb
Copy link
Contributor

sudeephb commented Dec 7, 2023

Currently this charm's only revision is under the name "bootstack-charmers-storage-connector" in charmhub. However, metadata.yaml reports the name "storage-connector" therefore juju is refusing to perform the upgrade operation since it thinks they are different charms.

$ juju refresh storage-connector --path=./storage-connector.charm
ERROR cannot refresh "bootstack-charmers-storage-connector" to "storage-connector"

On top of this when the name is changed in metadata.yaml, LXD build container fails with a message about the container name being too long.

...
Failed to launch instance 'charmcraft-bootstack-charmers-storage-connector-1045805-0-0-amd64'.
* Command that failed: "lxc --project charmcraft launch local:snapshot-craft-com.ubuntu.cloud-buildd-20.04-charmcraft-buildd-base-v0.0 local:charmcraft-bootstack-charmers-storage-connector-1045805-0-0-amd64 --config 'raw.idmap=both 1001 0' --config security.syscalls.intercept.mknod=true"
* Command exit code: 1
* Command output: b'Creating charmcraft-bootstack-charmers-storage-connector-1045805-0-0-amd64\n'
* Command standard error output: b'Error: Invalid instance name: Name must be 1-63 characters long\n'

...

Probably a name change in charmhub for this charm is a good idea.


Imported from Launchpad using lp2gh.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant