|
|
At first glance, it looks like your own broker server is returning 502 when CC attempts to issue the bind request. Do you see anything which corresponds to the request in your broker's logs? On Monday, August 22, 2016, Kumaresh Babu N S <kumareshcs20(a)gmail.com> wrote: Hi, I created haash service broker in out PCF environment. I created service instance for haash service and named as 'my-hash'. I can't bind 'my-hash' service instance with an app. I am getting following exception.
Error: Server error, status code: 502, error code: 10001, message: The service broker rejected the request to https://haash-broker.*****com/ v2/service_instances/187c8a7a-56f6-43b6-82a5-0912a86e95e4/ service_bindings/c150de2a-f5a3-4b73-8013-d088537a11d5. Status Code: 400 Bad Request, Body: {"timestamp":1471833736776,"error":"Bad Request","status":400,"message":""}
***** - domain name. Kindly do needful.
-- -- Marco Nicosia Product Manager Pivotal Software, Inc. mnicosia(a)pivotal.io c: 650-796-2948
|
|
No Marco. I got above exception when attempt to bind the service instance with an app.
|
|
Kumaresh, Marco meant you to check the logs of your Haash service broker app running on CF or elsewhere. If running on CF, issue cf logs <haash-service-broker-app> and from another window try the bind again and check the errors getting thrown by the broker. -Sabha On Tue, Aug 23, 2016 at 8:23 AM, Kumaresh Babu <kumareshcs20(a)gmail.com> wrote: No Marco. I got above exception when attempt to bind the service instance with an app.
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
|
|
Hi Sabha,
I got healthcheck passed status for haash-service-broker-app. It doesn't show errors in logs. What may be the problem?
Regards, Kumaresh
toggle quoted message
Show quoted text
On 23 August 2016 at 21:26, Sabha Parameswaran <sabhap(a)pivotal.io> wrote: Kumaresh,
Marco meant you to check the logs of your Haash service broker app running on CF or elsewhere. If running on CF, issue cf logs <haash-service-broker-app> and from another window try the bind again and check the errors getting thrown by the broker.
-Sabha
On Tue, Aug 23, 2016 at 8:23 AM, Kumaresh Babu <kumareshcs20(a)gmail.com> wrote:
No Marco. I got above exception when attempt to bind the service instance with an app.
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
|
|
Kumaresh, Continue to check the logs even as you issue the bind to app. Dont stop just with health check. Also, the logs get buffered for a bit before they show up in the cf logs. Retry the bind (or service creation) if needed till you see the request making it to the broker and any associated error. -Sabha On Tue, Aug 23, 2016 at 9:13 AM, Kumaresh Babu <kumareshcs20(a)gmail.com> wrote: Hi Sabha,
I got healthcheck passed status for haash-service-broker-app. It doesn't show errors in logs. What may be the problem?
Regards, Kumaresh
On 23 August 2016 at 21:26, Sabha Parameswaran <sabhap(a)pivotal.io> wrote:
Kumaresh,
Marco meant you to check the logs of your Haash service broker app running on CF or elsewhere. If running on CF, issue cf logs <haash-service-broker-app> and from another window try the bind again and check the errors getting thrown by the broker.
-Sabha
On Tue, Aug 23, 2016 at 8:23 AM, Kumaresh Babu <kumareshcs20(a)gmail.com> wrote:
No Marco. I got above exception when attempt to bind the service instance with an app.
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
|
|
I suspect you are getting tripped by new additional parameters being sent in the json payload during the bind request. Add following to the ServiceBinding code: @JsonIgnoreProperties(ignoreUnknown = true) This would ignore new unknown parameters. Rebuild the broker and redeploy and then try create service and bind. -Sabha On Tue, Aug 23, 2016 at 9:20 AM, Sabha Parameswaran <sabhap(a)pivotal.io> wrote: Kumaresh,
Continue to check the logs even as you issue the bind to app. Dont stop just with health check. Also, the logs get buffered for a bit before they show up in the cf logs. Retry the bind (or service creation) if needed till you see the request making it to the broker and any associated error.
-Sabha
On Tue, Aug 23, 2016 at 9:13 AM, Kumaresh Babu <kumareshcs20(a)gmail.com> wrote:
Hi Sabha,
I got healthcheck passed status for haash-service-broker-app. It doesn't show errors in logs. What may be the problem?
Regards, Kumaresh
On 23 August 2016 at 21:26, Sabha Parameswaran <sabhap(a)pivotal.io> wrote:
Kumaresh,
Marco meant you to check the logs of your Haash service broker app running on CF or elsewhere. If running on CF, issue cf logs <haash-service-broker-app> and from another window try the bind again and check the errors getting thrown by the broker.
-Sabha
On Tue, Aug 23, 2016 at 8:23 AM, Kumaresh Babu <kumareshcs20(a)gmail.com> wrote:
No Marco. I got above exception when attempt to bind the service instance with an app.
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
|
|
Sure Parameswaran. I will update the ServiceBinding code. I will try in our PCF environment and let you know.
toggle quoted message
Show quoted text
On 23 August 2016 at 22:51, Sabha Parameswaran <sabhap(a)pivotal.io> wrote: I suspect you are getting tripped by new additional parameters being sent in the json payload during the bind request. Add following to the ServiceBinding code:
@JsonIgnoreProperties(ignoreUnknown = true)
This would ignore new unknown parameters.
Rebuild the broker and redeploy and then try create service and bind.
-Sabha
On Tue, Aug 23, 2016 at 9:20 AM, Sabha Parameswaran <sabhap(a)pivotal.io> wrote:
Kumaresh,
Continue to check the logs even as you issue the bind to app. Dont stop just with health check. Also, the logs get buffered for a bit before they show up in the cf logs. Retry the bind (or service creation) if needed till you see the request making it to the broker and any associated error.
-Sabha
On Tue, Aug 23, 2016 at 9:13 AM, Kumaresh Babu <kumareshcs20(a)gmail.com> wrote:
Hi Sabha,
I got healthcheck passed status for haash-service-broker-app. It doesn't show errors in logs. What may be the problem?
Regards, Kumaresh
On 23 August 2016 at 21:26, Sabha Parameswaran <sabhap(a)pivotal.io> wrote:
Kumaresh,
Marco meant you to check the logs of your Haash service broker app running on CF or elsewhere. If running on CF, issue cf logs <haash-service-broker-app> and from another window try the bind again and check the errors getting thrown by the broker.
-Sabha
On Tue, Aug 23, 2016 at 8:23 AM, Kumaresh Babu <kumareshcs20(a)gmail.com> wrote:
No Marco. I got above exception when attempt to bind the service instance with an app.
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
|
|
Hi Parameswaran,
I have tried with the inputs provided. Still I am facing the same issue. The logs are attached for your review. Please suggest. Thanks.
Regards, Kumaresh
toggle quoted message
Show quoted text
On 24 August 2016 at 10:38, Kumaresh Babu <kumareshcs20(a)gmail.com> wrote: Sure Parameswaran. I will update the ServiceBinding code. I will try in our PCF environment and let you know.
On 23 August 2016 at 22:51, Sabha Parameswaran <sabhap(a)pivotal.io> wrote:
I suspect you are getting tripped by new additional parameters being sent in the json payload during the bind request. Add following to the ServiceBinding code:
@JsonIgnoreProperties(ignoreUnknown = true)
This would ignore new unknown parameters.
Rebuild the broker and redeploy and then try create service and bind.
-Sabha
On Tue, Aug 23, 2016 at 9:20 AM, Sabha Parameswaran <sabhap(a)pivotal.io> wrote:
Kumaresh,
Continue to check the logs even as you issue the bind to app. Dont stop just with health check. Also, the logs get buffered for a bit before they show up in the cf logs. Retry the bind (or service creation) if needed till you see the request making it to the broker and any associated error.
-Sabha
On Tue, Aug 23, 2016 at 9:13 AM, Kumaresh Babu <kumareshcs20(a)gmail.com> wrote:
Hi Sabha,
I got healthcheck passed status for haash-service-broker-app. It doesn't show errors in logs. What may be the problem?
Regards, Kumaresh
On 23 August 2016 at 21:26, Sabha Parameswaran <sabhap(a)pivotal.io> wrote:
Kumaresh,
Marco meant you to check the logs of your Haash service broker app running on CF or elsewhere. If running on CF, issue cf logs <haash-service-broker-app> and from another window try the bind again and check the errors getting thrown by the broker.
-Sabha
On Tue, Aug 23, 2016 at 8:23 AM, Kumaresh Babu <kumareshcs20(a)gmail.com
wrote: No Marco. I got above exception when attempt to bind the service instance with an app.
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
|
|
I need the cf logs output from the service broker app when you issue the bind request.
-Sabha
toggle quoted message
Show quoted text
On Wed, Aug 24, 2016 at 12:32 AM, <Phani_Kadali(a)dell.com> wrote: Hi sabha,
I have tried with the inputs provided. Still I am facing the same issue. The logs are attached for your review. Please suggest. Thanks
Regards Phani K
---------- Forwarded message ---------- From: Kumaresh Babu <kumareshcs20(a)gmail.com> Date: 24 August 2016 at 10:38 Subject: Re: [cf-dev] Re: Re: Re: Re: Re: Problem on binding service instance with an app To: "Discussions about Cloud Foundry projects and the system overall." < cf-dev(a)lists.cloudfoundry.org>
Sure Parameswaran. I will update the ServiceBinding code. I will try in our PCF environment and let you know.
On 23 August 2016 at 22:51, Sabha Parameswaran <sabhap(a)pivotal.io> wrote:
I suspect you are getting tripped by new additional parameters being sent in the json payload during the bind request. Add following to the ServiceBinding code:
@JsonIgnoreProperties(ignoreUnknown = true)
This would ignore new unknown parameters.
Rebuild the broker and redeploy and then try create service and bind.
-Sabha
On Tue, Aug 23, 2016 at 9:20 AM, Sabha Parameswaran <sabhap(a)pivotal.io> wrote:
Kumaresh,
Continue to check the logs even as you issue the bind to app. Dont stop just with health check. Also, the logs get buffered for a bit before they show up in the cf logs. Retry the bind (or service creation) if needed till you see the request making it to the broker and any associated error.
-Sabha
On Tue, Aug 23, 2016 at 9:13 AM, Kumaresh Babu <kumareshcs20(a)gmail.com> wrote:
Hi Sabha,
I got healthcheck passed status for haash-service-broker-app. It doesn't show errors in logs. What may be the problem?
Regards, Kumaresh
On 23 August 2016 at 21:26, Sabha Parameswaran <sabhap(a)pivotal.io> wrote:
Kumaresh,
Marco meant you to check the logs of your Haash service broker app running on CF or elsewhere. If running on CF, issue cf logs <haash-service-broker-app> and from another window try the bind again and check the errors getting thrown by the broker.
-Sabha
On Tue, Aug 23, 2016 at 8:23 AM, Kumaresh Babu <kumareshcs20(a)gmail.com
wrote: No Marco. I got above exception when attempt to bind the service instance with an app.
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
|
|
I got another email from Phani K, not sure if its same chain. Need the cf log output of the service broker that should report an exception when you issue the bind request to know the cause. -Sabha On Wed, Aug 24, 2016 at 1:56 AM, Kumaresh Babu <kumareshcs20(a)gmail.com> wrote: Hi Parameswaran,
I have tried with the inputs provided. Still I am facing the same issue. The logs are attached for your review. Please suggest. Thanks.
Regards, Kumaresh
On 24 August 2016 at 10:38, Kumaresh Babu <kumareshcs20(a)gmail.com> wrote:
Sure Parameswaran. I will update the ServiceBinding code. I will try in our PCF environment and let you know.
On 23 August 2016 at 22:51, Sabha Parameswaran <sabhap(a)pivotal.io> wrote:
I suspect you are getting tripped by new additional parameters being sent in the json payload during the bind request. Add following to the ServiceBinding code:
@JsonIgnoreProperties(ignoreUnknown = true)
This would ignore new unknown parameters.
Rebuild the broker and redeploy and then try create service and bind.
-Sabha
On Tue, Aug 23, 2016 at 9:20 AM, Sabha Parameswaran <sabhap(a)pivotal.io> wrote:
Kumaresh,
Continue to check the logs even as you issue the bind to app. Dont stop just with health check. Also, the logs get buffered for a bit before they show up in the cf logs. Retry the bind (or service creation) if needed till you see the request making it to the broker and any associated error.
-Sabha
On Tue, Aug 23, 2016 at 9:13 AM, Kumaresh Babu <kumareshcs20(a)gmail.com> wrote:
Hi Sabha,
I got healthcheck passed status for haash-service-broker-app. It doesn't show errors in logs. What may be the problem?
Regards, Kumaresh
On 23 August 2016 at 21:26, Sabha Parameswaran <sabhap(a)pivotal.io> wrote:
Kumaresh,
Marco meant you to check the logs of your Haash service broker app running on CF or elsewhere. If running on CF, issue cf logs <haash-service-broker-app> and from another window try the bind again and check the errors getting thrown by the broker.
-Sabha
On Tue, Aug 23, 2016 at 8:23 AM, Kumaresh Babu < kumareshcs20(a)gmail.com> wrote:
No Marco. I got above exception when attempt to bind the service instance with an app.
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
|
|
One request throws a 400 while other shows the status as 201. PUT /v2/service_instances/539c383d-2388-4676-a6ac- f53658d14e61/service_bindings
Can you share your app code or any changes you have made so I can test it locally?
-Sabha
toggle quoted message
Show quoted text
On Wed, Aug 24, 2016 at 3:31 PM, <Phani_Kadali(a)dell.com> wrote: Hi Sabha,
Below are the logs
Getting console contents. Please wait...
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
2016-08-24 22:24:07.112 WARN 23 --- [nio-8080-exec-5] o.s.c.s.ResourceBundleMessageSource : ResourceBundle [messages] not found for MessageSource: Can't find bundle for base name messages, locale en_US
2016-08-24 22:24:07.113 INFO 23 --- [nio-8080-exec-5] o.s.b.a.audit.listener.AuditListener : AuditEvent [timestamp=Wed Aug 24 22:24:07 UTC 2016, principal=warreng, type=AUTHENTICATION_SUCCESS, data={details=org.springframework.security.web.authentication. WebAuthenticationDetails(a)ffff6a82: RemoteIpAddress: 52.193.149.28; SessionId: null}]
haash-broker-dell-withdrawable-embankment.system.dellcloudcoe.com - [24/08/2016:22:24:07 +0000] "PUT /v2/service_instances/ 71cf0cdd-92fd-473d-9056-fcf06dbc4ce3/service_bindings/ 76d1121a-5a50-40bb-af95-4633dd37581c HTTP/1.1" 400 157 75 "-" "HTTPClient/1.0 (2.6.0.1, ruby 2.2.3 (2015-08-18))" 10.0.0.53:16816 x_forwarded_for:"52.193.149.28" x_forwarded_proto:"http" vcap_request_id:f9b136e7-8f42-4b31-6cc4-83e48ed4859a response_time:0.009304013 app_id:facccdf0-487f-4748-a51a-aa50d44c0785
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
2016-08-24 22:24:56.864 WARN 23 --- [nio-8080-exec-8] o.s.c.s.ResourceBundleMessageSource : ResourceBundle [messages] not found for MessageSource: Can't find bundle for base name messages, locale en_US
2016-08-24 22:24:56.865 INFO 23 --- [nio-8080-exec-8] o.s.b.a.audit.listener.AuditListener : AuditEvent [timestamp=Wed Aug 24 22:24:56 UTC 2016, principal=warreng, type=AUTHENTICATION_SUCCESS, data={details=org.springframework.security.web.authentication. WebAuthenticationDetails(a)ffff6a82: RemoteIpAddress: 52.193.149.28; SessionId: null}]
Hibernate: select service0_.id as id1_4_, service0_.bindable as bindable2_4_, service0_.description as descript3_4_, service0_.name as name4_4_ from services service0_
Hibernate: select plans0_.service_id as service_4_4_0_, plans0_.id as id1_1_0_, plans0_.id as id1_1_1_, plans0_.description as descript2_1_1_, plans0_.name as name3_1_1_ from plans plans0_ where plans0_.service_id=?
haash-broker-dell-withdrawable-embankment.system.dellcloudcoe.com - [24/08/2016:22:24:56 +0000] "GET /v2/catalog HTTP/1.1" 200 0 171 "-" "HTTPClient/1.0 (2.6.0.1, ruby 2.2.3 (2015-08-18))" 10.0.0.174:35796 x_forwarded_for:"52.193.149.28" x_forwarded_proto:"https" vcap_request_id:1ff5651f-32a3-4d87-5b1c-c0ad17d6c3a8 response_time:0.012625324 app_id:facccdf0-487f-4748-a51a-aa50d44c0785
healthcheck passed
Exit status 0
2016-08-24 22:25:39.338 WARN 23 --- [nio-8080-exec-1] o.s.c.s.ResourceBundleMessageSource : ResourceBundle [messages] not found for MessageSource: Can't find bundle for base name messages, locale en_US
2016-08-24 22:25:39.339 INFO 23 --- [nio-8080-exec-1] o.s.b.a.audit.listener.AuditListener : AuditEvent [timestamp=Wed Aug 24 22:25:39 UTC 2016, principal=warreng, type=AUTHENTICATION_SUCCESS, data={details=org.springframework.security.web.authentication. WebAuthenticationDetails(a)ffff6a82: RemoteIpAddress: 52.193.149.28; SessionId: null}]
Hibernate: select count(*) as col_0_0_ from service_instances serviceins0_ where serviceins0_.id=? and 1=1
Hibernate: select serviceins0_.id as id1_3_0_, serviceins0_.organization_guid as organiza2_3_0_, serviceins0_.plan_id as plan_id3_3_0_, serviceins0_.service_id as service_4_3_0_, serviceins0_.space_guid as space_gu5_3_0_ from service_instances serviceins0_ where serviceins0_.id=?
Hibernate: insert into service_instances (organization_guid, plan_id, service_id, space_guid, id) values (?, ?, ?, ?, ?)
haash-broker-dell-withdrawable-embankment.system.dellcloudcoe.com - [24/08/2016:22:25:39 +0000] "PUT /v2/service_instances/ 539c383d-2388-4676-a6ac-f53658d14e61?accepts_incomplete=true HTTP/1.1" 201 150 2 "-" "HTTPClient/1.0 (2.6.0.1, ruby 2.2.3 (2015-08-18))" 10.0.0.174:35796 x_forwarded_for:"52.193.149.28" x_forwarded_proto:"https" vcap_request_id:f2f6c0da-8b85-4d48-58dd-ecb3d7254701 response_time:0.014983969 app_id:facccdf0-487f-4748-a51a-aa50d44c0785
2016-08-24 22:25:48.472 WARN 23 --- [nio-8080-exec-3] o.s.c.s.ResourceBundleMessageSource : ResourceBundle [messages] not found for MessageSource: Can't find bundle for base name messages, locale en_US
2016-08-24 22:25:48.473 INFO 23 --- [nio-8080-exec-3] o.s.b.a.audit.listener.AuditListener : AuditEvent [timestamp=Wed Aug 24 22:25:48 UTC 2016, principal=warreng, type=AUTHENTICATION_SUCCESS, data={details=org.springframework.security.web.authentication. WebAuthenticationDetails(a)ffff6a82: RemoteIpAddress: 52.193.149.28; SessionId: null}]
Hibernate: select serviceins0_.id as id1_3_0_, serviceins0_.organization_guid as organiza2_3_0_, serviceins0_.plan_id as plan_id3_3_0_, serviceins0_.service_id as service_4_3_0_, serviceins0_.space_guid as space_gu5_3_0_ from service_instances serviceins0_ where serviceins0_.id=?
2016-08-24 22:25:48.479 INFO 23 --- [nio-8080-exec-3] c.m.c.h.c.ServiceBrokerController : Instance details:::::::::::com.mattstine.cf.haash.model. ServiceInstance(a)b5d209d3
Hibernate: select serviceins0_.id as id1_3_, serviceins0_.organization_guid as organiza2_3_, serviceins0_.plan_id as plan_id3_3_, serviceins0_.service_id as service_4_3_, serviceins0_.space_guid as space_gu5_3_ from service_instances serviceins0_
2016-08-24 22:25:48.481 INFO 23 --- [nio-8080-exec-3] c.m.c.h.c.ServiceBrokerController : :::si.getId():::::539c383d-2388-4676-a6ac-f53658d14e61::: ::::::si.getServiceId():::::3221
Hibernate: select count(*) as col_0_0_ from service_instances serviceins0_ where serviceins0_.id=? and 1=1
2016-08-24 22:25:48.483 INFO 23 --- [nio-8080-exec-3] c.m.c.h.c.ServiceBrokerController : ::::serviceInstanceRepository.exists(instanceId)::::true
Hibernate: select count(*) as col_0_0_ from service_instances serviceins0_ where serviceins0_.id=? and 1=1
Hibernate: select count(*) as col_0_0_ from service_instances serviceins0_ where serviceins0_.id=? and 1=1
Hibernate: select count(*) as col_0_0_ from service_bindings servicebin0_ where servicebin0_.id=? and 1=1
2016-08-24 22:25:48.488 INFO 23 --- [nio-8080-exec-3] c.m.c.h.c.ServiceBrokerController : :::::::::::::::1::::::::::::::::
2016-08-24 22:25:48.488 INFO 23 --- [nio-8080-exec-3] c.m.c.h.c.ServiceBrokerController : :::::::::::::::5::::::::::::::::
Hibernate: select servicebin0_.id as id1_2_1_, servicebin0_.app_guid as app_guid2_2_1_, servicebin0_.service_binding_id as service_6_2_1_, servicebin0_.instance_id as instance3_2_1_, servicebin0_.plan_id as plan_id4_2_1_, servicebin0_.service_id as service_5_2_1_, credential1_.id as id1_0_0_, credential1_.password as password2_0_0_, credential1_.uri as uri3_0_0_, credential1_.username as username4_0_0_ from service_bindings servicebin0_ left outer join credentials credential1_ on servicebin0_.service_binding_id=credential1_.id where servicebin0_.id=?
Hibernate: select credential0_.id as id1_0_0_, credential0_.password as password2_0_0_, credential0_.uri as uri3_0_0_, credential0_.username as username4_0_0_ from credentials credential0_ where credential0_.id=?
Hibernate: insert into credentials (password, uri, username, id) values (?, ?, ?, ?)
Hibernate: insert into service_bindings (app_guid, service_binding_id, instance_id, plan_id, service_id, id) values (?, ?, ?, ?, ?, ?)
haash-broker-dell-withdrawable-embankment.system.dellcloudcoe.com - [24/08/2016:22:25:48 +0000] "PUT /v2/service_instances/ 539c383d-2388-4676-a6ac-f53658d14e61/service_bindings/ 77d03c44-4c14-4cbd-a5e1-f4032df23c36 HTTP/1.1" 201 39 184 "-" "HTTPClient/1.0 (2.6.0.1, ruby 2.2.3 (2015-08-18))" 10.0.0.53:16862 x_forwarded_for:"52.193.149.28" x_forwarded_proto:"https" vcap_request_id:a29f7270-f640-4ddc-6098-c50de63a326c response_time:0.026780822 app_id:facccdf0-487f-4748-a51a-aa50d44c0785
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
2016-08-24 22:28:40.542 WARN 23 --- [nio-8080-exec-1] o.s.c.s.ResourceBundleMessageSource : ResourceBundle [messages] not found for MessageSource: Can't find bundle for base name messages, locale en_US
2016-08-24 22:28:40.543 INFO 23 --- [nio-8080-exec-1] o.s.b.a.audit.listener.AuditListener : AuditEvent [timestamp=Wed Aug 24 22:28:40 UTC 2016, principal=warreng, type=AUTHENTICATION_SUCCESS, data={details=org.springframework.security.web.authentication. WebAuthenticationDetails(a)ffff6a82: RemoteIpAddress: 52.193.149.28; SessionId: null}]
haash-broker-dell-withdrawable-embankment.system.dellcloudcoe.com - [24/08/2016:22:28:40 +0000] "PUT /v2/service_instances/ 539c383d-2388-4676-a6ac-f53658d14e61/service_bindings/ daa77ea7-2669-4cb2-94cd-f4aba4fa0aeb HTTP/1.1" 400 157 75 "-" "HTTPClient/1.0 (2.6.0.1, ruby 2.2.3 (2015-08-18))" 10.0.0.174:35824 x_forwarded_for:"52.193.149.28" x_forwarded_proto:"https" vcap_request_id:df3c6c9b-6d57-4742-6fc4-6a05c18c75bc response_time:0.012537932 app_id:facccdf0-487f-4748-a51a-aa50d44c0785
healthcheck passed
Exit status 0
healthcheck passed
Exit status 0
------------------------------ *From:* Sabha Parameswaran [sabhap(a)pivotal.io] *Sent:* Wednesday, August 24, 2016 9:14 AM *To:* Kadali, Phani *Cc:* Discussions about Cloud Foundry projects and the system overall.; Raveendir, Ashokkumar
*Subject:* Re: [cf-dev] Re: Re: Re: Re: Re: Problem on binding service instance with an app
I need the cf logs output from the service broker app when you issue the bind request.
-Sabha
On Wed, Aug 24, 2016 at 12:32 AM, <Phani_Kadali(a)dell.com> wrote:
Hi sabha,
I have tried with the inputs provided. Still I am facing the same issue. The logs are attached for your review. Please suggest. Thanks
Regards Phani K
---------- Forwarded message ---------- From: Kumaresh Babu <kumareshcs20(a)gmail.com> Date: 24 August 2016 at 10:38 Subject: Re: [cf-dev] Re: Re: Re: Re: Re: Problem on binding service instance with an app To: "Discussions about Cloud Foundry projects and the system overall." < cf-dev(a)lists.cloudfoundry.org>
Sure Parameswaran. I will update the ServiceBinding code. I will try in our PCF environment and let you know.
On 23 August 2016 at 22:51, Sabha Parameswaran <sabhap(a)pivotal.io> wrote:
I suspect you are getting tripped by new additional parameters being sent in the json payload during the bind request. Add following to the ServiceBinding code:
@JsonIgnoreProperties(ignoreUnknown = true)
This would ignore new unknown parameters.
Rebuild the broker and redeploy and then try create service and bind.
-Sabha
On Tue, Aug 23, 2016 at 9:20 AM, Sabha Parameswaran <sabhap(a)pivotal.io> wrote:
Kumaresh,
Continue to check the logs even as you issue the bind to app. Dont stop just with health check. Also, the logs get buffered for a bit before they show up in the cf logs. Retry the bind (or service creation) if needed till you see the request making it to the broker and any associated error.
-Sabha
On Tue, Aug 23, 2016 at 9:13 AM, Kumaresh Babu <kumareshcs20(a)gmail.com> wrote:
Hi Sabha,
I got healthcheck passed status for haash-service-broker-app. It doesn't show errors in logs. What may be the problem?
Regards, Kumaresh
On 23 August 2016 at 21:26, Sabha Parameswaran <sabhap(a)pivotal.io> wrote:
Kumaresh,
Marco meant you to check the logs of your Haash service broker app running on CF or elsewhere. If running on CF, issue cf logs <haash-service-broker-app> and from another window try the bind again and check the errors getting thrown by the broker.
-Sabha
On Tue, Aug 23, 2016 at 8:23 AM, Kumaresh Babu < kumareshcs20(a)gmail.com> wrote:
No Marco. I got above exception when attempt to bind the service instance with an app.
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
-- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554
|
|
Phani K is my team mate. We are working to solve the issue.
|
|