This charm needs to be a subordinate charm
Bug #1971609 reported by
Steven Parker
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| charm-fstab-config |
Fix Released
|
Undecided
|
Aliaksandr Vasiuk | ||
Bug Description
When we expand units we need this charm to be a subordinate not a principle charm so that all application deployments will get the fstab changes. This will also simplify new bundle development.
The issue is that we can make changes to specific nodes that may host a specific application but we would loss those custom changes when we add new units to the cloud. It complicates the day two maintenance of these applications.
Related branches
~valexby/charm-fstab-config:bug/1971609-subordinate
- Sudeep Bhandari: Approve
- Eric Chen: Approve
- 🤖 prod-jenkaas-bootstack (community): Approve (continuous-integration)
- BootStack Reviewers: Pending requested
-
Diff: 82 lines (+21/-6)5 files modifiedMakefile (+2/-1)
charmcraft.yaml (+4/-1)
src/metadata.yaml (+5/-1)
src/tests/functional/tests/bundles/base.yaml (+6/-2)
src/tests/functional/tests/tests.yaml (+4/-1)
| Changed in charm-fstab-config: | |
| assignee: | nobody → Aliaksandr Vasiuk (valexby) |
| status: | New → In Progress |
| Changed in charm-fstab-config: | |
| milestone: | none → 23.01 |
| status: | In Progress → Fix Committed |
| Changed in charm-fstab-config: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
