cancel
Showing results for 
Search instead for 
Did you mean: 

Cloud Foundry Trial: Failed to bind HDI container

former_member231229
Participant

Hello everyone,

Anyone else is experiencing issues with hdi-container service binding?
I have an application which was working just fine until yesterday, and today all of a sudden I am unable to perform a database build. It terminates with:

Could not bind resource for module '/db'. CF-ServiceBrokerBadResponse(10001): Service broker error: Failed to bind container 'XXXXXXX_YYYYYYY_HDI_CONTAINER' on database '4e7659f0-cbae-4064-afb7-12f9d2b21ec8:trialdb01' (10.253.93.93:30041), because of: Failed to check existence of container 'XXXXXXX_YYYYYYY_HDI_CONTAINER', because of: SAP DBTech JDBC: [258]: insufficient privilege: Not authorized

I was wondering if maybe this was caused by something I did, so I just generated a new application using the wizard and built it without changes:

Could not create service key required for 'Bookshop-Bookshop-hdi-container-C5Fl2KYVX1VetO4zHm' instance of the 'hanatrial' service type for the 'Bookshop-hdi-container' resource. CF-ServiceBrokerBadResponse(10001): Service broker error: Failed to bind container 'BOOKSHOP_BOOKSHOP_HDI_CONTAINER_133' on database '4e7659f0-cbae-4064-afb7-12f9d2b21ec8:trialdb01' (10.253.93.93:30041), because of: Failed to check existence of container 'BOOKSHOP_BOOKSHOP_HDI_CONTAINER_133', because of: SAP DBTech JDBC: [258]: insufficient privilege: Not authorized

Different error, but same reason (Not authorized).

Does anyone know what is happening?

Thanks,

Roberto.

lsubatin
Active Contributor
0 Kudos

Same error here and trying to figure out what is going on...

former_member231229
Participant
0 Kudos

lsubatin Might it be some kind of maintenance? System status seems fine for all datacenters...it happened suddenly today, around noon (Italian time).

former_member231229
Participant
0 Kudos

New error, now on the Node.Js service:

23:41:06 (DIBuild) 

[INFO] Target platform is CF
[INFO] Reading mta.yaml
[INFO] Processing mta.yaml
[INFO] Processing module xxx-app
[INFO] Processing module xxx-db
[INFO] Processing module xxx-srv
[INFO] Logs of build task for module xxx-app:>
./start_grunt.sh: line 10: npm: command not found>
/usr/bin/env: 'node': No such file or directory
[ERROR] Failed to build module xxx-app.

No "node" found.

Accepted Solutions (0)

Answers (3)

Answers (3)

I have a similar error which I have posted here. Like your problem, it occured suddenly yesterday afternoon.

former_member235482
Participant

Having the exact same issue when attempting to deploy a simple app from web IDE for Hana and from the cmd CF CLI. I was able to successfully deploy this exact .mtar to HANA Express XSA. Is this a known issue with depploying to CF or do I really have an authorization error on my trial account?

Web IDE for HANA Deploy Failure:

Preparing to deploy /mta_archives/administration/administration_0.0.1.mtar
Checking if there are conflicting processesFound 1 conflicting processes
Aborting process 54664245Uploading archiveStarting deploymentDetected MTA schema version: "3"
Deploying in org "S0012398093trial_trial" and space "dev"
No deployed MTA detected - this is initial deploymentDetected new MTA version: "0.0.1"
Creating service "administration-hdi-container" from MTA resource "administration-hdi-container"...
Service "administration-hdi-container" creation with service offering "hana" failed with "403 Forbidden: A service instance for the selected plan cannot be created in this organization. The plan is visible because another organization you belong to has access to it."0 of 1 done, (1 creating)0 of 1 done, (1 creating)0 of 1 done, (1 creating)1 of 1 done

Creating application "db" from MTA module "db"...Error creating application "db": Could not bind application "db" to service "administration-hdi-container": 502 Bad Gateway: Service broker error: Failed to bind container '4275B5FF72854788BE57B446506AA351' on database '4e7659f0-cbae-4064-afb7-12f9d2b21ec8:trialdb01' (<IP>), because of: Failed to check existence of container '4275B5FF72854788BE57B446506AA351', because of: SAP DBTech JDBC: [258]: insufficient privilege: Not authorizedUnexpected error: Could not bind application "db" to service "administration-hdi-container": 502 Bad Gateway: Service broker error: Failed to bind container '4275B5FF72854788BE57B446506AA351' on database '4e7659f0-cbae-4064-afb7-12f9d2b21ec8:trialdb01' (<IP>), because of: Failed to check existence of container '4275B5FF72854788BE57B446506AA351', because of: SAP DBTech JDBC: [258]: insufficient privilege: Not authorizedJob failed
4:04:08 PM (DeploymentToCF) Deployment of the "administration" project to Cloud Foundry failed.(Response state is FAILED)

CF CLI Bind-Service to CF Trial Account Failure:

C:\Users\Admin>cf bind-service db administration-hdi-container
Binding service administration-hdi-container to app db in org <SNumber>trial_trial / space dev as <email>...
Unexpected Response
Response code: 502
CC code:       0
CC error code:
Request ID:    32037bea-8c0b-49e4-45d2-96f56169706c::c6618f8c-2044-4cf2-a03c-19fc35a96866
Description:   {
  "description": "Service broker error: Failed to bind container '4275B5FF72854788BE57B446506AA351' on database '4e7659f0-cbae-4064-afb7-12f9d2b21ec8:trialdb01' (<IP>), because of: Failed to check existence of container '4275B5FF72854788BE57B446506AA351', because of: SAP DBTech JDBC: [258]: insufficient privilege: Not authorized",
  "error_code": "CF-ServiceBrokerBadResponse",
  "code": 10001,
  "http": {
    "uri": "https://hana-broker-trial.cfapps.eu10.hana.ondemand.com/v2/service_instances/df5c0e79-c64d-4532-98b4-d40a24fcf59b/service_bindings/d8d15385-f83f-4713-937b-4c2651358fd7?accepts_incomplete=true",
    "method": "PUT",
    "status": 500
  }
}


FAILED
former_member231229
Participant
0 Kudos

Hello Austin,

I was curious too and I quickly summoned up a local HANA Express instance on my laptop.
It took 10 seconds to build and deploy the project successfully on it.

This seems to be an issue with CF itself.

lsubatin
Active Contributor
0 Kudos

Yes, engineering is looking into it.

lsubatin
Active Contributor
0 Kudos

It's working again now volker1987 austinkloske r.pagni

former_member231229
Participant
0 Kudos

I confirm it is working now.

Thanks for the update lsubatin