-
Notifications
You must be signed in to change notification settings - Fork 67
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
It looks like PR#1126 may have broken reactive builds; metadata.yaml is overwritten? #1150
Comments
Hi, do you able to give me the repo of that reactive charm? |
Sure, yes. it's https://opendev.org/openstack/charm-mysql-innodb-cluster However, I'm converting it to a binary reactive charm (with lunar support), which is where I hit the issue: https://review.opendev.org/c/openstack/charm-mysql-innodb-cluster/+/886634 However, it should be reproducible with any charmcraft charm that uses the reactive plugin (note the review 886634 uses the reactive plugin, the master branch doesn't (yet)). Thanks. |
The reactive framework uses an incompatible variant that creates its own files. The format defined by charmcraft cannot be used. Fix: #1150
Thanks very much for the fix @syu-w ! |
@ajkavanagh do you able to confirm it is working now? |
@syu-w I can confirm that I've built the mysql-innodb-cluster charm with |
Bug Description
It looks like PR#1126 may have broken charm-build (the reactive builders)
metadata.yaml
creation, as it seems to immediately overwrite it. This is with --channel=latest/edge (2.3.0.post16+gited81be8). At least I think that is what may be going on. I was testing latest/edge for the ability to build on lunar (23.04).The offending line appears to be at
charmcraft/charmcraft/commands/build.py
Line 181 in ed81be8
The issue is that the built charms' metadata should look like this:
but actually looks like this:
To Reproduce
Environment
charmcraft.yaml
Relevant log output
The text was updated successfully, but these errors were encountered: