Merge lp:~james-page/charms/trusty/rabbitmq-server/fixup-configure-nodename into lp:~openstack-charmers-archive/charms/trusty/rabbitmq-server/next
| Status: | Merged |
|---|---|
| Merged at revision: | 99 |
| Proposed branch: | lp:~james-page/charms/trusty/rabbitmq-server/fixup-configure-nodename |
| Merge into: | lp:~openstack-charmers-archive/charms/trusty/rabbitmq-server/next |
| Diff against target: |
12 lines (+2/-0) 1 file modified
hooks/rabbitmq_server_relations.py (+2/-0) |
| To merge this branch: | bzr merge lp:~james-page/charms/trusty/rabbitmq-server/fixup-configure-nodename |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| charmers | 2015-07-16 | Pending | |
|
Review via email:
|
|||
This proposal supersedes a proposal from 2015-07-16.
Description of the Change
Fixup missing configuration of local nodename, causing problems when forward/reverse dns is broken.
charm_unit_test #5910 rabbitmq-
UNIT OK: passed
charm_amulet_test #5132 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 #5912 rabbitmq-
UNIT OK: passed
charm_lint_check #6280 rabbitmq-
LINT OK: passed
| Ryan Beisner (1chb1n) wrote : | # |
Tested this with the same scenario, and it fails at the same place.
charm_amulet_test #5134 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://
| Ryan Beisner (1chb1n) wrote : | # |
Please see the following proposal which resolves the deploy issues we were seeing in lxc on baremetal:
PS thanks for the jump start.

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