receptor domain and callback issues

[davebotelho]

hi guys, I've uploaded a the diego release .789 and .817 to my microbosh and have deployed both successfully. I've noticed that there are numerous references to the services.dc1.consul domain in various spec files, likely for dev purposes but not sure. in my manifest, I've had to change the diego_api_url to reference the actual IP of the receptor server (cell_z1) in order for my cf push's to get partially completed. They get through the retrieval of the buildpacks but fail at the callback to the stager. I see this reference in the stager logs.

"callback_url":"http://stager.service.dc1.consul:8888",

Should this domain be an attribute in the manifest so that I can easily use the domain of my cf releases haproxy? Also, I've tried adding the domain of the haproxy as the diego_api_url but have run into issues where the haproxy doesn't know where to even send it. Maybe I'm just doing it wrong. Thoughts?

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/87148284.

[fraenkel]

You have to be current on both cf-release and diego-release to make things work.
Our latest green build for diego-release was 0.843 which was paired with cf-release@a43654bfa526c9bf9162932c1c1364c7f43cdb18

That callback_url is correct. We are using consul as a means for service discovery which is internal only.
Everything should just work if you are following the README in diego-release.

You will need to provide more details as to what is failing. But first I would upgrade to the latest code on both sides.

[onsi]

@davebotelho - let us know if you still have issues after upgrading.