Autowakeup acceptance tests failing in develop branch

[pradyutsarma]

We are working on a postgres port for autosleep and with the first version, one of the acceptance tests failed as in the trace below.

1) Incoming traffic will trigger app restart a sleeping appl :: = ... | FAIL | Expected error 'Invalid status code 503' but got 'Invalid status code 404'.

The entire test trace is in the attached file. More importantly, the tests are also failing with mysql too. I'm not that well versed with the py tests and the autowakeup feature. I am guessing from the 404 instead of 503 that the autowakeup is not really 'waking up' the app. Need some ideas here.

test_trace.txt

[gberche-orange]

Hi Pradyut,

Good to hear you’re making progress on the pg support. Did you deploy the autowake up application, and bound the wildcard route associated to the domain used by the test app [1] ?

Can you please send privately a content of the produced reports (*.html) in particular logs.html that would provide additional details ?

Thanks,

Guillaume.

[1] https://github.com/cloudfoundry-community/autosleep/blob/develop/doc/publish.md#deploy-autosleep-app

---

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

[pradyutsarma]

Thanks @gberche-orange . I will ping you via email.

[gberche-orange]

@pradyutsarma did you bind the wildcard route to the autowake up application as documented into https://github.com/cloudfoundry-community/autosleep/blob/develop/doc/publish.md#deploy-autosleep-app ?

I see from the logs you sent you're using a bosh-lite instance. Can you manually test that orphan traffic (i.e traffic associated with a route on a stopped app) is indeed received by the autowake up application ?

If not, make sure your DNS setting is properly resolving to your CF deployment haproxy/gorouter.

( Running the acceptance tests within our environment on mysql results in the report on http://cloudfoundry-community.github.io/autosleep/ )

[gberche-orange]

@pradyutsarma ping

[pradyutsarma]

This was a configuration problem due to which the tests were timing out. Already resolved.