Fwd: [Canonical-juju-qa] Cursed (final): #1173 lp:juju-core r2511 (manual-deploy)

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 14-03-31 08:47 AM, Curtis Hovey-Canonical wrote:
> The tests show that the wordpress charm failed to present a web
> page. Juju status reports there was nothing wrong with juju or the
> charm. We have no logs for the failure.
> 
> Aaron will capture some logs of what is wrong and investigate
> issues with CI. Can someone investigate Juju?

I'm pretty confident that this was a CI issue, not Juju.

The manual provider test works by creating instances in EC2 using the
euca tools.  It relies on the fact that the default security group
allows machines within it to talk to each other on arbitrary ports.

For some reason, our default security group was no longer configured
to allow machines to communicate on any port.  This meant that
WordPress hung when it tried to connect to the MySQL server-- there
was no longer any access to port 3306.

I added a rule to permit access to port 3306 for machines in the
default group, which solves the immediate problem.  It seems to me
that the manual provider tests would be more reliable if they had
their own security group, because such a group would rarely need to be
updated, and would be clearly linked to the test.  I've added a new
"manual-juju-test" group, and I plan to configure the test to use it
instead of the default group.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTOc9VAAoJEK84cMOcf+9h0dcH/ihUYyBTSLmsa1SS4H2xpMMF
8dvH9maf4p60vf84yLkAFWpGChUVfvDkFr0VDuzh0B/Gf/miUSy93FjA3ySkH/in
8G1K0C+2O300LxMiK8WUnhcpZ/QICvjoAIsgSGyYe0BitS3zUUYf3O3gkmmZOflj
zmykYAdV3BGeOxjv8mXG3TBOoNIis/qQE+7iUTsui/kNOcrPTqWMEhRVhZ9VaAfW
V5nEipzLVR/o6JsU5fBPxUuUZe9Ls+PFkm86FCQWMfdO0Ap+y4k4BHodR0kUi/TF
8zz8VgvKxPxwvepmHgqN8kwJaoQpLU3Mfagfa8gDoz/eroaOsGncBcs2w7NefIU=
=obE+
-----END PGP SIGNATURE-----