we are facing this issue a lot of times between 8.30am CET and 9.30am CET. After 9.30 it is working again, can you help us to figure out and the solution of this issue. why it is not always working between 8.30 and 9.30
open source Jenkins CI.
And this not limited to one container and getting on multiple containers. kindly let us know solution approach
Hello,
Apologies for the late response. Is this issue still applicable? Could you share the "cf dmol" logs for further investigation.
Best regards,
Ivan
Description
we are facing this issue a lot of times between 8.30am CET and 9.30am CET. After 9.30 it is working again, can you help us to figure out and the solution of this issue. why it is not always working between 8.30 and 9.30 open source Jenkins CI.
And this not limited to one container and getting on multiple containers. kindly let us know solution approach
Error from Jenkins: Gateway: CF-ServiceBrokerBadResponse(10001): Service broker error: Service broker hana-broker failed with: could not reach service broker hana-broker at https://hana-broker.cf.eu20.hana.ondemand.com/v2/service_instances/d5f7cd21-9078-4ea4-9b31-52acdffbdaf1/service_bindings/42a44068-49be-4f09-8401-be7102208135
[2022-10-10T07:06:29.961Z] Error while binding service instance "hdi_ecc" to application "sc_r4r_db": Could not bind service "hdi_ecc" to application "sc_r4r_db": 502 Bad Gateway: CF-ServiceBrokerBadResponse(10001): Service broker error: Service broker hana-broker failed with: could not reach service broker hana-broker at https://hana-broker.cf.eu20.hana.ondemand.com/v2/service_instances/0e7bb3b0-a4c0-4358-81dc-030ee1f22d6e/service_bindings/31ad652b-2aef-4d8c-bff7-ea8bbfd859ae
[2022-10-10T07:06:29.961Z] Error while binding service instance "hdi_secobs" to application "sc_r4r_db": Could not bind service "hdi_secobs" to application "sc_r4r_db": 502 Bad Gateway: CF-ServiceBrokerBadResponse(10001): Service broker error: Service broker hana-broker failed with: could not reach service broker hana-broker at https://hana-broker.cf.eu20.hana.ondemand.com/v2/service_instances/a8f5867c-f6a6-4a56-8c89-64bcff0d60b9/service_bindings/c6d66994-dcaf-4abd-a6c2-d202bbc7a02b
[2022-10-10T07:06:29.961Z] Proceeding with automatic retry... (3 of 3 attempts left)
[2022-10-10T07:06:29.961Z] Binding service instance "hdi_sc_r4r" to application "sc_r4r_db"...
[2022-10-10T07:06:29.961Z] Binding service instance "hdi_ecc" to application "sc_r4r_db"...
[2022-10-10T07:06:29.961Z] Binding service instance "hdi_secobs" to application "sc_r4r_db"...
[2022-10-10T07:06:31.887Z] Error while binding service instance "hdi_r4r" to application "sc_r4r_db": Could not bind service "hdi_r4r" to application "sc_r4r_db": 502 Bad Gateway: CF-ServiceBrokerBadResponse(10001): Service broker error: Service broker hana-broker failed with: could not reach service broker hana-broker at https://hana-broker.cf.eu20.hana.ondemand.com/v2/service_instances/30e19cfc-c743-4807-8948-0121c2dacb27/service_bindings/2d9de929-3f1f-41e6-b08a-710c1c42e143
[2022-10-10T07:06:31.887Z] Error while binding service instance "hdi_sc_md" to application "sc_r4r_db": Could not bind service "hdi_sc_md" to application "sc_r4r_db": 502 Bad Gateway: CF-ServiceBrokerBadResponse(10001): Service broker error: Service broker hana-broker failed with: could not reach service broker hana-broker at https://hana-broker.cf.eu20.hana.ondemand.com/v2/service_instances/38e18e9d-dc26-4b10-8eaa-d63287531b4d/service_bindings/e1b57fe2-cccb-4e9a-928c-676b07bbc3c5
[2022-10-10T07:06:31.887Z] Proceeding with automatic retry... (2 of 3 attempts left)
[2022-10-10T07:06:32.151Z] Binding service instance "hdi_r4r" to application "sc_r4r_db"...
[2022-10-10T07:06:32.151Z] Binding service instance "hdi_sc_md" to application "sc_r4r_db"...
[2022-10-10T07:09:08.863Z] Error while binding service instance "hdi_sc_se" to application "sc_r4r_db": Could not bind service "hdi_sc_se" to application "sc_r4r_db": 502 Bad Gateway: CF-ServiceBrokerBadResponse(10001): Service broker error: Service broker hana-broker failed with: could not reach service broker hana-broker at https://hana-broker.cf.eu20.hana.ondemand.com/v2/service_instances/ddcaf5c8-1fbd-4461-96bc-ea2af62a169a/service_bindings/2350a3b0-ba43-4fc6-9634-e0bfbd9b32b1
[2022-10-10T07:09:08.863Z] Proceeding with automatic retry... (1 of 3 attempts left)
[2022-10-10T07:09:08.863Z] Binding service instance "hdi_sc_se" to application "sc_r4r_db"...
[2022-10-10T07:09:30.947Z] Error while binding service instance "hdi_secobs" to application "sc_r4r_db": Could not bind service "hdi_secobs" to application "sc_r4r_db": 502 Bad Gateway: CF-ServiceBrokerBadResponse(10001): Service broker error: Service broker hana-broker failed with: could not reach service broker hana-broker at https://hana-broker.cf.eu20.hana.ondemand.com/v2/service_instances/a8f5867c-f6a6-4a56-8c89-64bcff0d60b9/service_bindings/ff078ac7-2dee-4628-a3f5-fee9034468a0
[2022-10-10T07:09:30.947Z] Error while binding service instance "hdi_sc_r4r" to application "sc_r4r_db": Could not bind service "hdi_sc_r4r" to application "sc_r4r_db": 502 Bad Gateway: CF-ServiceBrokerBadResponse(10001): Service broker error: Service broker hana-broker failed with: could not reach service broker hana-broker at https://hana-broker.cf.eu20.hana.ondemand.com/v2/service_instances/d5f7cd21-9078-4ea4-9b31-52acdffbdaf1/service_bindings/af81acdf-d713-4a72-9de6-aa828059050b
[2022-10-10T07:09:30.947Z] Error while binding service instance "hdi_ecc" to application "sc_r4r_db": Could not bind service "hdi_ecc" to application "sc_r4r_db": 502 Bad Gateway: CF-ServiceBrokerBadResponse(10001): Service broker error: Service broker hana-broker failed with: could not reach service broker hana-broker at https://hana-broker.cf.eu20.hana.ondemand.com/v2/service_instances/0e7bb3b0-a4c0-4358-81dc-030ee1f22d6e/service_bindings/e861379b-cb73-45af-894a-084a389ef391
[2022-10-10T07:09:30.947Z] Process failed.
[2022-10-10T07:09:30.947Z] Use "cf deploy -i a0b7333f-4869-11ed-8d3a-eeee0a9741df -a abort" to abort the process.
[2022-10-10T07:09:30.947Z] Use "cf deploy -i a0b7333f-4869-11ed-8d3a-eeee0a9741df -a retry" to retry the process.
[2022-10-10T07:09:30.947Z] Use "cf dmol -i a0b7333f-4869-11ed-8d3a-eeee0a9741df" to download the logs of the process.
kindly let us know any further additional information required.
Thanks in Advance!
build_log.txt operation_log.txt