Merge lp:~james-page/charms/trusty/rabbitmq-server/status-check into lp:~openstack-charmers-archive/charms/trusty/rabbitmq-server/next
| Status: | Merged |
|---|---|
| Merged at revision: | 116 |
| Proposed branch: | lp:~james-page/charms/trusty/rabbitmq-server/status-check |
| Merge into: | lp:~openstack-charmers-archive/charms/trusty/rabbitmq-server/next |
| Diff against target: |
261 lines (+131/-18) 3 files modified
hooks/rabbit_utils.py (+67/-16) hooks/rabbitmq_server_relations.py (+7/-0) unit_tests/test_rabbit_utils.py (+57/-2) |
| To merge this branch: | bzr merge lp:~james-page/charms/trusty/rabbitmq-server/status-check |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| David Ames | Approve on 2015-10-05 | ||
| James Page | Resubmit on 2015-10-05 | ||
|
Review via email:
|
|||
Description of the Change
Add basic use of status feature in Juju
This includes:
1) Evaluation of current rabbitmq state on the server using 'status'
2) Evaluation of cluster status once peers appear on the cluster relation
3) status set when installing packages and when configuring mirroring (long ops)
I also found a race in leader-
charm_unit_test #10358 rabbitmq-
UNIT OK: passed
charm_amulet_test #6934 rabbitmq-
AMULET FAIL: amulet-test failed
AMULET Results (max last 2 lines):
make: *** [functional_test] Error 124
ERROR:root:Make target returned non-zero.
Full amulet test output: http://
Build: http://
| David Ames (thedac) wrote : | # |
I really like the workgroup status approach in this MP.
I also like your solution to https:/
mkdir is imported in hooks/rabbitmq_
I also really like breaking out clustered() as a cached function on its own. However, one of the bugs I am fighting (https:/
if len(running_
Consider, the 3rd, 4th and 5th nodes to attempt clustering. There will already by 2+ running nodes and they will assume incorrectly they are already clustered.
In my testing I have removed this check entirely with some success. I would be interested in finding a more robust clustered check.
I plan to merge your MP into my branch and do some more testing and see if I can come up with a clustered check that works in all cases.
charm_amulet_test #6937 rabbitmq-
AMULET FAIL: amulet-test failed
AMULET Results (max last 2 lines):
2015-10-01 21:19:58,241 publish_
ERROR:root:Make target returned non-zero.
Full amulet test output: http://
Build: http://
| David Ames (thedac) wrote : | # |
> However, one of the bugs I am fighting
> (https:/
> direct result of checking for more than one running node.
>
> if len(running_
>
> Consider, the 3rd, 4th and 5th nodes to attempt clustering. There will already
> by 2+ running nodes and they will assume incorrectly they are already
> clustered.
Ignore this. I see what it is supposed to do. As the local unit will only ever see 1 if not clustered or more if clustered.
> I plan to merge your MP into my branch and do some more testing and see if I
> can come up with a clustered check that works in all cases.
I am testing a combination of my MP which ignores min-cluster-size when leadership election is available and your MP now. I'll see if any more race conditions reveal themselves.
charm_amulet_test #6938 rabbitmq-
AMULET FAIL: amulet-test failed
AMULET Results (max last 2 lines):
make: *** [functional_test] Error 1
ERROR:root:Make target returned non-zero.
Full amulet test output: http://
Build: http://
charm_lint_check #11156 rabbitmq-
LINT OK: passed
Build: http://
charm_unit_test #10364 rabbitmq-
UNIT OK: passed
charm_amulet_test #6970 rabbitmq-
AMULET FAIL: amulet-test failed
AMULET Results (max last 2 lines):
make: *** [functional_test] Error 1
ERROR:root:Make target returned non-zero.
Full amulet test output: http://
Build: http://
charm_lint_check #11169 rabbitmq-
LINT OK: passed
Build: http://
charm_unit_test #10372 rabbitmq-
UNIT OK: passed
charm_amulet_test #6992 rabbitmq-
AMULET FAIL: amulet-test failed
AMULET Results (max last 2 lines):
make: *** [functional_test] Error 124
ERROR:root:Make target returned non-zero.
Full amulet test output: http://
Build: http://
charm_amulet_test #7002 rabbitmq-
AMULET FAIL: amulet-test failed
AMULET Results (max last 2 lines):
make: *** [functional_test] Error 1
ERROR:root:Make target returned non-zero.
Full amulet test output: http://
Build: http://
charm_amulet_test #7009 rabbitmq-
AMULET FAIL: amulet-test failed
AMULET Results (max last 2 lines):
make: *** [functional_test] Error 1
ERROR:root:Make target returned non-zero.
Full amulet test output: http://
Build: http://
charm_amulet_test #7025 rabbitmq-
AMULET FAIL: amulet-test failed
AMULET Results (max last 2 lines):
make: *** [functional_test] Error 1
ERROR:root:Make target returned non-zero.
Full amulet test output: http://
Build: http://
charm_unit_test #10521 rabbitmq-
UNIT OK: passed
charm_lint_check #11327 rabbitmq-
LINT OK: passed
Build: http://
charm_amulet_test #7112 rabbitmq-
AMULET OK: passed
Build: http://

charm_lint_check #11153 rabbitmq- server- next for james-page mp273037
LINT OK: passed
Build: http:// 10.245. 162.77: 8080/job/ charm_lint_ check/11153/