Invalid config charm ceph-mon expected-osd-count=3
Bug #1743460 reported by
Ryan Beisner
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Openstack Mojo Testing |
Fix Released
|
Critical
|
Ryan Beisner | ||
Bug Description
After this Jan 4 commit, many mojo specs are failing.
http://
http://
00:02:27.762 2018-01-06 05:49:39 [INFO] deployer.cli: Starting deployment of trusty-liberty
00:02:27.762 2018-01-06 05:49:39 [DEBUG] deployer.import: Getting charms...
00:02:27.762 2018-01-06 05:49:39 [WARNING] deployer.charm: Invalid charm specification ceph-mon
00:02:27.762 2018-01-06 05:49:42 [DEBUG] deployer.deploy: Resolving configuration
00:02:27.762 2018-01-06 05:49:43 [ERROR] deployer.deploy: Invalid config charm ceph-mon expected-
Related branches
lp:~1chb1n/openstack-mojo-specs/revert323
- Andrew McLeod (community): Approve
- OpenStack Charm Testing Maintainers: Pending requested
-
Diff: 1829 lines (+171/-891)34 files modifiedhelper/bundles/designate.yaml (+0/-386)
helper/bundles/full-dvr-next.yaml (+3/-3)
helper/bundles/full-next.yaml (+112/-163)
helper/bundles/full-ssl-next.yaml (+3/-3)
helper/bundles/full-ssl.yaml (+3/-3)
helper/bundles/full.yaml (+3/-3)
helper/bundles/ha-next.yaml (+3/-3)
helper/bundles/ha.yaml (+3/-3)
helper/bundles/haphase1-next.yaml (+3/-3)
helper/bundles/haphase1.yaml (+3/-3)
helper/bundles/haphase2-next.yaml (+3/-3)
helper/bundles/haphase2.yaml (+3/-3)
helper/bundles/ksv3-full-next.yaml (+3/-3)
helper/bundles/ksv3-full.yaml (+3/-3)
helper/collect/collect-next-ha (+3/-1)
helper/collect/collect-next-trusty (+3/-1)
helper/collect/collect-next-xenial (+4/-7)
helper/collect/collect-stable-ha (+3/-1)
helper/collect/collect-stable-ha-trusty (+3/-1)
helper/collect/collect-stable-trusty (+3/-1)
helper/collect/collect-stable-xenial (+3/-1)
helper/scripts/get_floating_ip.py (+0/-30)
helper/setup/configure-designate.sh (+0/-9)
helper/setup/designate_setup.py (+0/-108)
helper/tests/validate-designate.sh (+0/-10)
helper/utils/mojo_os_utils.py (+1/-16)
specs/full_stack/next_deploy_designate/mitaka/SPEC_INFO.txt (+0/-2)
specs/full_stack/next_deploy_designate/mitaka/manifest (+0/-28)
specs/full_stack/next_deploy_designate/newton/SPEC_INFO.txt (+0/-2)
specs/full_stack/next_deploy_designate/newton/manifest (+0/-28)
specs/full_stack/next_deploy_designate/ocata/SPEC_INFO.txt (+0/-2)
specs/full_stack/next_deploy_designate/ocata/manifest (+0/-28)
specs/full_stack/next_deploy_designate/pike/SPEC_INFO.txt (+0/-2)
specs/full_stack/next_deploy_designate/pike/manifest (+0/-28)
Revision history for this message
| Ryan Beisner (1chb1n) wrote | #1 |
| Changed in openstack-mojo-specs: | |
| importance: | Undecided → Critical |
| assignee: | nobody → David Ames (thedac) |
Revision history for this message
| Ryan Beisner (1chb1n) wrote | #2 |
Revision history for this message
| Ryan Beisner (1chb1n) wrote | #3 |
| Changed in openstack-mojo-specs: | |
| assignee: | David Ames (thedac) → Ryan Beisner (1chb1n) |
| status: | New → In Progress |
Revision history for this message
| Andrew McLeod (admcleod) wrote | #4 |
| Changed in openstack-mojo-specs: | |
| status: | In Progress → Fix Committed |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I looked at the MP diff but it is a bit of a monster and I didn't have cycles to t-shoot. With test automation blocked, I'm in favor of reverting the change and having it resubmitted for review again. It should then be exercised in OSCI as part of that.
Here is a merge proposal to revert:
lp:~1chb1n/openstack-mojo-specs/revert323