configuration scripts fail when using juju 2.0
Bug #1616124 reported by
Felipe Reyes
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Charm Testing |
Fix Released
|
Undecided
|
Felipe Reyes | ||
Bug Description
post-deploy-config uses 'juju status' assuming the output will be yaml and that assumption is wrong for juju 2.0. Also juju 2.0 renamed "set" to "set-config".
tools/*.sh use 'juju set' for {ram,cpu}
Related branches
lp://staging/~freyes/openstack-charm-testing/fix-post-deploy
- Ryan Beisner: Needs Information
-
Diff: 25 lines (+8/-3)1 file modifiedbin/post-deploy-config (+8/-3)
lp://staging/~freyes/openstack-charm-testing/fix-tools
- Ryan Beisner: Needs Information
-
Diff: 41 lines (+9/-5)3 files modifiedtools/quota_high.sh (+4/-2)
tools/quota_million.sh (+4/-2)
tools/sec_groups.sh (+1/-1)
| Changed in openstack-charm-testing: | |
| assignee: | nobody → Felipe Reyes (freyes) |
| status: | New → In Progress |
| tags: | added: sts |
Revision history for this message
| Felipe Reyes (freyes) wrote | #1 |
| summary: |
- post-deploy-config fails when using juju 2.0 + configuration scripts fail when using juju 2.0 |
| description: | updated |
Revision history for this message
| Ryan Beisner (1chb1n) wrote | #2 |
| Changed in openstack-charm-testing: | |
| status: | In Progress → Incomplete |
Revision history for this message
| Dan Streetman (ddstreet) wrote | #3 |
| Changed in openstack-charm-testing: | |
| status: | Incomplete → Fix Released |
To post a comment you must log in.
Making this bug report a bit more generic to address all the changes needed to support juju 2.0