Failing to create-service when autosleep hosted behind buddy-broker for --shared-scope

[drnic]

Failing to create-service when autosleep hosted behind buddy-broker for --shared-scope

[gberche-orange]

Would make sense to trace the provision request proxified by the buddy broker as it reaches the autosleep app, maybe consider adding a verbose trace mode to buddy broker ?

Maybe the https://github.com/cloudfoundry-samples/logging-route-service could be mapped to the autosleep route to trace incoming traffic.

On the autosleep side, you might have luck with spring traces, or possibly further down such as tomcat.

There used to have support for dumping requests in tomcat, but it was broken last time I tested it, see https://groups.google.com/a/cloudfoundry.org/d/msg/vcap-dev/8bm0IDAZNHU/MS3yUN3whm0J

Maybe the TRACE actuator endpoint could provide you detailed traces of the last recorded 1000 requests, I haven't tested it yet on autosleep though.

The -Dautosleep.debug=spring would turn spring traces

autosleep/common/src/main/resources/logback.xml

Lines 39 to 48 in 08f8d66

	<logger name="org.springframework">
	<if condition='property("autosleep.debug").contains("spring")'>
	<then>
	<level value="DEBUG"/>
	</then>
	<else>
	<level value="WARN"/>
	</else>
	</if>
	</logger>

Otherwise you can select individual log level through the JAVA_OPTS option

autosleep/manifest.tmpl.yml

Lines 18 to 19 in 180f4f1

	JAVA_OPTS: >
	-Dlogging.level.org.springframework.web.filter.CommonsRequestLoggingFilter=ERROR

Please let us know how you diagnosed this, so we can document it for other diagnostics

[drnic]

I tried out the logging-route-service but hit a DNS/cloudflare issue cloudfoundry/logging-route-service#3

Seen this before?

[drnic]

Ok, worked around the cloudflare issue by using cfapps.io domain for autosleep/autowakeup-app.

I can now see that buddy-broker is mis-processing the parameters being passed thru.

The logging-route logs incoming into buddy-broker: are:

2017-01-08T15:21:42.98-0800 [APP/PROC/WEB/0]OUT 2017/01/08 23:21:42 Request Body: {"service_id":"3e02929c-d253-11e6-8921-032a782f98e5-starkandwayne-stannis","plan_id":"41e3ba08-d253-11e6-a8b0-67ab01c15319-starkandwayne-stannis","organization_guid":"f18dd8a3-bea3-4078-953a-e3a768520818","space_guid":"b7d9e138-23b0-4578-b81e-181c11afd524","parameters":{"auto-enrollment":"forced"}}

But when the request is forwarded on to autosleep-app, the parameters are misencoded:

2017-01-08T15:28:03.57-0800 [APP/PROC/WEB/0]OUT 2017/01/08 23:28:03 Request Body: {"service_id":"3e02929c-d253-11e6-8921-032a782f98e5","plan_id":"41e3ba08-d253-11e6-a8b0-67ab01c15319","organization_guid":"f18dd8a3-bea3-4078-953a-e3a768520818","space_guid":"b7d9e138-23b0-4578-b81e-181c11afd524","parameters":"eyJhdXRvLWVucm9sbG1lbnQiOiJmb3JjZWQifQ=="}

Closing the issue; and moving it to buddy-broker repo cloudfoundry-community/buddy-broker#3

[gberche-orange]

thanks @drnic for sharing the diagnostic procedure and outcome.

I'm not sure to understand why the logging route service issue with the cloudflare error symptom triggers on autosleep.starkandwayne.com and not autosleep.cfapps.io.