Charm fails to build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL Router Charm |
Triaged
|
Low
|
Unassigned |
Bug Description
I suspect the override-stage: workaround in charmcraft.yaml is no longer working
```
:: charmtools.
:: charmtools.
:: charmtools.
:: charmtools.
:: charmtools.
:: utils: b'3728340\n'
:: utils: process: git describe --dirty --always (0)
:: charmtools.
:: build:
:: build: -------
:: build: Build Report
:: build: -------
:: build: New build; all files were modified.
:: build: Cleaning up /root/.
:: proof: I: `display-name` not provided, add for custom naming in the UI
:: proof: I: config.yaml: option ssl_cert has no default value
:: proof: I: config.yaml: option ssl_key has no default value
:: proof: I: config.yaml: option ssl_ca has no default value
:: _______
:: build-reactive: commands succeeded
:: congratulations :)
Running step STAGE for part 'charm'
Execute action
:: /bin/bash: line 30: CHARMCRAFT_STAGE: unbound variable
Parts processing error: 'override-stage' in part 'charm' failed with code 1.
Review the scriptlet and make sure it's correct.
Failed to build charm for bases index '0'.
```
I have seen the same workaround in other charms as well. I'm sure they will all fail.
But why are the overrides even necessary? charmcraft has a reactive plugin.
CHARMCRAFT_ PART_BUILD is also unbound