Merge lp:~freyes/charms/trusty/memcached/lp1525026 into lp:charms/trusty/memcached
| Status: | Superseded |
|---|---|
| Proposed branch: | lp:~freyes/charms/trusty/memcached/lp1525026 |
| Merge into: | lp:charms/trusty/memcached |
| Diff against target: |
82 lines (+18/-8) 2 files modified
tests/10_deploy_test.py (+6/-3) tests/20_deploy_replication_test.py (+12/-5) |
| To merge this branch: | bzr merge lp:~freyes/charms/trusty/memcached/lp1525026 |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Review Queue (community) | automated testing | Needs Fixing on 2016-03-10 | |
| Adam Israel | 2015-12-22 | Needs Fixing on 2016-01-28 | |
| charmers | 2016-02-12 | Pending | |
|
Review via email:
|
|||
This proposal has been superseded by a proposal from 2016-02-25.
Description of the Change
Open firewall to allow non-related machines to connect
memcached charm by default secures their units with ufw, this is intended to
avoid non-related units connect to memcached, because it's a security risk.
This patch makes sure that unit testing scripts have the ability to connect
to memcached, after it's verified that the testing script couldn't connect
the memcached port is open running (ufw insert 1 allow PORT)
make functional_test -> http://
charm_unit_test #14769 memcached for freyes mp281254
UNIT OK: passed
charm_amulet_test #8386 memcached for freyes mp281254
AMULET OK: passed
Build: http://
| Review Queue (review-queue) wrote : | # |
This item has failed automated testing! Results available here http://
| Review Queue (review-queue) wrote : | # |
This item has failed automated testing! Results available here http://
charm_lint_check #16581 memcached for freyes mp281254
LINT OK: passed
Build: http://
charm_unit_test #15483 memcached for freyes mp281254
UNIT OK: passed
charm_amulet_test #8507 memcached for freyes mp281254
AMULET OK: passed
Build: http://
| Felipe Reyes (freyes) wrote : | # |
On Sat, 26 Dec 2015 14:39:31 -0000
Review Queue <email address hidden> wrote:
> Review: Needs Fixing automated testing
>
> This item has failed automated testing! Results available here
> http://
Sadly the logs aren't available anymore, but running locally I got no
errors for LXC
$ bundletester -e lxc
memcached
charm-proof PASS
make lint PASS
make test PASS
00_setup.sh PASS
10_
INFO:deployer.env: Waiting for machine termination
20_
PASS: 6 Total: 6 (549.816231 sec)
--
Felipe Reyes
Software Sustaining Engineer @ Canonical
STS Engineering Team
# Email: <email address hidden> (GPG:0x9B1FFF39)
# Phone: +56 9 7640 7887
# Launchpad: ~freyes | IRC: freyes
| Marco Ceppi (marcoceppi) wrote : | # |
I've requeued the tests
On Tue, Jan 5, 2016 at 2:27 PM Felipe Reyes <email address hidden>
wrote:
> On Sat, 26 Dec 2015 14:39:31 -0000
> Review Queue <email address hidden> wrote:
>
> > Review: Needs Fixing automated testing
> >
> > This item has failed automated testing! Results available here
> > http://
>
> Sadly the logs aren't available anymore, but running locally I got no
> errors for LXC
>
> $ bundletester -e lxc
> memcached
> charm-proof
> PASS
> make lint
> PASS
> make test
> PASS
> 00_setup.sh
> PASS
> 10_deploy_test.py
> PASS
> INFO:deployer.env: Waiting for machine termination
> 20_deploy_
> PASS
>
> PASS: 6 Total: 6 (549.816231 sec)
>
>
> --
> Felipe Reyes
> Software Sustaining Engineer @ Canonical
> STS Engineering Team
> # Email: <email address hidden> (GPG:0x9B1FFF39)
> # Phone: +56 9 7640 7887
> # Launchpad: ~freyes | IRC: freyes
>
>
> https:/
> You are reviewing the proposed merge of
> lp:~freyes/charms/trusty/memcached/lp1525026 into
> lp:charms/trusty/memcached.
>
| Review Queue (review-queue) wrote : | # |
This item has failed automated testing! Results available here http://
| Review Queue (review-queue) wrote : | # |
This item has failed automated testing! Results available here http://
| Adam Israel (aisrael) wrote : | # |
I ran fresh tests on LXC and Amazon yesterday, and both failed.
I think I fixed the tests on LXC (it works locally for me now), by setting allow-ufw-
https:/
Tests are still failing on Amazon, unfortunately. Here's the bundletester output; I added some extra output in the failure to illustrate what's happening:
http://
It looks like it's comparing a private against a public address.
Please let me know if you need any other information or you'd like me to retest.
| Review Queue (review-queue) wrote : | # |
The results (PASS) are in and available here: http://
| Review Queue (review-queue) wrote : | # |
This item has failed automated testing! Results available here http://
| Review Queue (review-queue) wrote : | # |
This item has failed automated testing! Results available here http://
| Review Queue (review-queue) wrote : | # |
This item has failed automated testing! Results available here http://
- 72. By Felipe Reyes on 2016-02-25
-
Get private-address using 'juju run'
UnitSentry doesn't populate the 'info' dict with the private-address, so
to check if the replication was properly configured in clouds where
private-address is different from the public-address, the former is retrieved
with 'juju run ... unit-get private-address'
| Review Queue (review-queue) wrote : | # |
This item has failed automated testing! Results available here http://

charm_lint_check #15824 memcached for freyes mp281254
LINT OK: passed
Build: http:// 10.245. 162.77: 8080/job/ charm_lint_ check/15824/