cf-mysql-release Acceptance test failing


Daya Shetty <daya.shetty@...>
 

Deployed bosh-lite version of cf-mysql-release version 22 successfully , but the acceptance test is failing with the following error:

[2015-08-12 05:24:04.76 (UTC)]> curl -s -d myvalue http://2f9a9ccf-818d-4c3a-7e70-f34f46c1b9d8.10.244.0.34.xip.io/service/mysql/e8cfc2c1-5301-4907-522f-ab6d23215c37/mykey
Error: Can't connect to MySQL server on '10.244.7.6' (111)

• Failure [87.711 seconds]
P-MySQL Lifecycle Tests
/var/vcap/packages/acceptance-tests/src/github.com/cloudfoundry-incubator/cf-mysql-acceptance-tests/cf-mysql-service/lifecycle/lifecycle_test.go:55
Allows users to create, bind, write to, read from, unbind, and destroy a service instance for the each plan [It]
/var/vcap/packages/acceptance-tests/src/github.com/cloudfoundry-incubator/cf-mysql-acceptance-tests/cf-mysql-service/lifecycle/lifecycle_test.go:54

Got stuck at:
Error: Can't connect to MySQL server on '10.244.7.6' (111)

The VM’s are running fine..

Deployment `cf-warden-mysql'

Director task 706

Task 706 done

+----------------------+---------+--------------------+--------------+
| Job/index | State | Resource Pool | IPs |
+----------------------+---------+--------------------+--------------+
| cf-mysql-broker_z1/0 | running | cf-mysql-broker_z1 | 10.244.7.130 |
| cf-mysql-broker_z2/0 | running | cf-mysql-broker_z2 | 10.244.8.130 |
| mysql_z1/0 | running | mysql_z1 | 10.244.7.2 |
| mysql_z2/0 | running | mysql_z2 | 10.244.8.2 |
| mysql_z3/0 | running | mysql_z3 | 10.244.9.2 |
| proxy_z1/0 | running | proxy_z1 | 10.244.7.6 |
| proxy_z2/0 | running | proxy_z2 | 10.244.8.6 |
+----------------------+---------+--------------------+--------------+

VMs total: 7

Any reason why the client is getting Connection Refused error while trying to connect to proxy_z1?

Thanks
Daya


Marco Nicosia
 

Hi there,

There are two ways to install CF on a bosh-lite. Depending on how you've installed CF, we may be able to help you.

If you've used bosh-lite's provision_cf script (https://github.com/cloudfoundry/bosh-lite/blob/master/docs/deploy-cf.md#single-command-deploy), it may be an issue with your security groups. This is a known issue, and you can fix the security groups by following these instructions:
https://gist.github.com/menicosia/2e9c414430138064f945#file-sg-steps-md

We're likely to send a PR about this to bosh-lite soon.

However, if you've used the manual deploy steps (https://github.com/cloudfoundry/bosh-lite/blob/master/docs/deploy-cf.md#manual-deploy), you shouldn't have this problem. Please let us know which method you've used to install CF, and hopefully we can help you from there.

--
Marco Nicosia
Product Manager
Pivotal Software, Inc.
mnicosia(a)pivotal.io


Shetty, Daya <Daya.Shetty@...>
 

Hi Marco,

Yes, I did run the provision_cf script hence did not have the security
group defined for mysql. Once I added that the acceptance-tests did pass.

Thanks again,
Daya

On 8/19/15, 10:14 AM, "Marco N." <mnicosia(a)pivotal.io> wrote:

Hi there,

There are two ways to install CF on a bosh-lite. Depending on how you've
installed CF, we may be able to help you.

If you've used bosh-lite's provision_cf script
(https://github.com/cloudfoundry/bosh-lite/blob/master/docs/deploy-cf.md#s
ingle-command-deploy), it may be an issue with your security groups. This
is a known issue, and you can fix the security groups by following these
instructions:
https://gist.github.com/menicosia/2e9c414430138064f945#file-sg-steps-md

We're likely to send a PR about this to bosh-lite soon.

However, if you've used the manual deploy steps
(https://github.com/cloudfoundry/bosh-lite/blob/master/docs/deploy-cf.md#m
anual-deploy), you shouldn't have this problem. Please let us know which
method you've used to install CF, and hopefully we can help you from
there.

--
Marco Nicosia
Product Manager
Pivotal Software, Inc.
mnicosia(a)pivotal.io
The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses.

Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities.