Errand Broker Deployer for Spring Cloud Services Failed

[sabri trabelsi]

Hello,

 

I Got this error on Ops Manager while deploying Spring Cloud Services Tile 1.5.4 : [31mNo container can run this application. Please ensure that you've pushed a valid JVM artifact or artifacts using the -p command line argument or path manifest entry. Information about valid JVM artifacts can be found at https://github.com/cloudfoundry/java-buildpack#additional-documentation. [0m

[31mFailed to compile droplet: Failed to run finalize script: exit status 1[0m

 

Any idea please ?

 

Thanks !

[Daniel Mikusa]

What is the output of `cf buildpacks` on your system? Can you provide a larger snippet of logs?

[sabri trabelsi]

Please find attached the logs and the output of cf buildpacks.

For your information i tried java buildpack v4.8, v4.10, 4.11 and 4.12, same error.

 

Thanks

[sabri trabelsi]

Please find attached the output of cf buildpacks

[Daniel Mikusa]

The error is indicating that the application bits, i.e. the SCS broker worker, are not detected by the Java buildpack as a valid Java app (i.e. the Java buildpack doesn't know how to run the app). Since this app is coming from the SCS tile & it's being pushed by the SCS errand & we test this extensively, this shouldn't generally happen. The app bits should always be good and should get pushed in a consistent way.

 

The only thing that stands at as different at this point is that it's referencing an online buildpack. We don't normally see that because the SCS tile will default to use the Java buildpack that ships with the platform. Please go into Ops Manager -> SCS Tile -> Settings -> SCS and change the Buildpack option to `java_buildpack_offline`. This should use the default buildpack, not one from the Internet. Save & apply changes. Let me know if the problem persists.

 

Thanks

[Daniel Mikusa]

OK, thanks for trying that. I'm checking to see if I can replicate this issue in our labs.

[sabri trabelsi]

hello Daniel,

 

Thanks for your response.

I tried to put "java_buildpack_offline" as you said, but i got the same error.

 

[Daniel Mikusa]

I have not been able to reproduce this in our labs. My suggestion going forward would be to open up a support ticket and Pivotal can work more closely with you to debug this problem. Please reference this community thread from the ticket, as that will provide context to whomever is assigned to the ticket. Thanks!

[TDF OPS]

Ok, thanks for your help.

I just opened a support ticket.

 

Have a nice day !