Open JDK Like Memory Calculator error: No version resolvable for ... #328
Description
This is related to my trailing comments at the end of issue 327.
I attempted to use v3.7 of the Java Buildpack with a test application. However, I'm receiving the following:
stackato[fence]: Prepared Docker container
stackato[cloud_controller_ng]: Updated app 'push-test-application' -- {"console"=>true, "state"=>"STARTED"}
staging: -----> Downloaded app package (18M)
staging: Cloning into '/tmp/buildpacks/java-buildpack'...
staging: Note: checking out '74974a971ac957f7bae29e5fa7c1b1613fa92c6f'.
staging:
staging: You are in 'detached HEAD' state. You can look around, make experimental
staging: changes and commit them, and you can discard any commits you make in this
staging: state without impacting any branches by performing another checkout.
staging:
staging: If you want to create a new branch to retain commits you create, you may
staging: do so (now or later) by using -b with the checkout command again. Example:
staging:
staging: git checkout -b new_branch_name
staging:
staging: [ConfigurationUtils] DEBUG Configuration from /tmp/buildpacks/java-buildpack/config/version.yml: {"version"=>"v3.7"}
staging: [BuildpackVersion] DEBUG v3.7 | https://github.com/cloudfoundry/java-buildpack#74974a9
...
staging: [DownloadCache] DEBUG Request: /memory-calculator/precise/x86_64/index.yml, {"accept"=>["*/*"], "user-agent"=>["Ruby"]}
staging: [DownloadCache] DEBUG Response headers: {"content-type"=>["text/x-yaml"], "content-length"=>["578"], "connection"=>["keep-alive"], "date"=>["Fri, 02 Sep 2016 14:12:59 GMT"], "last-modified"=>["Mon, 02 Nov 2015 11:44:59 GMT"], "etag"=>["\"57768197fb57b794b75904df5b4cf334\""], "x-amz-version-id"=>["null"], "accept-ranges"=>["bytes"], "server"=>["AmazonS3"], "age"=>["8148"], "x-cache"=>["Hit from cloudfront"], "via"=>["1.1 8ba75adf2ce5d1824a6bd830b1c26122.cloudfront.net (C
loudFront)"], "x-amz-cf-id"=>["wym0461B8r91N7w7DpG0dyqYZJTkVNHT-Hx88emjQW1WqbErx1FhGA=="]}
staging: [DownloadCache] DEBUG Response status: 200
staging: [DownloadCache] DEBUG Persisting etag: "57768197fb57b794b75904df5b4cf334"
staging: [DownloadCache] DEBUG Persisting last-modified: Mon, 02 Nov 2015 11:44:59 GMT
staging: [DownloadCache] DEBUG Persisting content to /tmp/https%3A%2F%2Fdownload.run.pivotal.io%2Fmemory-calculator%2Fprecise%2Fx86_64%2Findex.yml.cached
staging: [DownloadCache] DEBUG Validated content size 578 is 578
staging: [RepositoryIndex] DEBUG {"1.0.0_RELEASE"=>"https://download.run.pivotal.io/memory-calculator/precise/x86_64/memory-calculator-1.0.0_RELEASE", "1.1.0_RELEASE"=>"https://download.run.pivotal.io/memory-calculator/precise/x86_64/memory-calculator-1.1.0_RELEASE", "1.1.1_RELEASE"=>"https://download.run.pivotal.io/memory-calculator/precise/x86_64/memory-calculator-1.1.1_RELEASE", "2.0.0_RELEASE"=>"https://download.run.pivotal.io/memory-calculator/precise/x86_64/memory-calculator
-2.0.0_RELEASE.tar.gz", "2.0.1_RELEASE"=>"https://download.run.pivotal.io/memory-calculator/precise/x86_64/memory-calculator-2.0.1_RELEASE.tar.gz"}
staging: [Buildpack] ERROR Compile failed with exception #<RuntimeError: Open JDK Like Memory Calculator error: No version resolvable for '2.0.2_RELEASE' in 1.0.0_RELEASE, 1.1.0_RELEASE, 1.1.1_RELEASE, 2.0.0_RELEASE, 2.0.1_RELEASE>
staging: [Buildpack] DEBUG Exception #<RuntimeError: Open JDK Like Memory Calculator error: No version resolvable for '2.0.2_RELEASE' in 1.0.0_RELEASE, 1.1.0_RELEASE, 1.1.1_RELEASE, 2.0.0_RELEASE, 2.0.1_RELEASE> backtrace:
In the middle section omitted from the logs above I see this line:
staging: [RepositoryIndex] DEBUG {default.repository.root}/memory-calculator/{platform}/{architecture} expanded to https://download.run.pivotal.io/memory-calculator/precise/x86_64
If I look at that repository index file, I don't see 2.0.2_RELEASE which would account for the error.
When I try to use the Java Buildpack master instead of v3.6 I get a similar exception, however, regarding Open JDK versions:
staging: [RepositoryIndex] DEBUG {default.repository.root}/openjdk/{platform}/{architecture} expanded to https://java-buildpack.cloudfoundry.org/openjdk/precise/x86_64
...
staging: [Buildpack] ERROR Compile failed with exception #<RuntimeError: Open Jdk JRE error: No version resolvable for '1.8.0_10+' in 1.7.0_01, 1.7.0_02, 1.7.0_03, 1.7.0_04, 1.7.0_05, 1.7.0_06, 1.7.0_07, 1.7.0_08, 1.7.0_09, 1.7.0_10, 1.7.0_11, 1.7.0_12, 1.7.0_13, 1.7.0_14, 1.7.0_15, 1.7.0_17, 1.7.0_21, 1.7.0_25, 1.7.0_40, 1.7.0_45, 1.7.0_51, 1.7.0_55, 1.7.0_60, 1.7.0_65, 1.8.0_00, 1.8.0_05, 1.8.0_11, 1.8.0_20, 1.8.0_M6, 1.8.0_M7, 1.8.0_M8, 1.8.0_RC1, 1.8.0_25, 1.7.0_71, 1.8.
0_31, 1.7.0_75, 1.8.0_40, 1.8.0_45, 1.7.0_79, 1.8.0_51, 1.8.0_60, 1.8.0_65, 1.8.0_71, 1.8.0_73>
staging: [Buildpack] DEBUG Exception #<RuntimeError: Open Jdk JRE error: No version resolvable for '1.8.0_10+' in 1.7.0_01, 1.7.0_02, 1.7.0_03, 1.7.0_04, 1.7.0_05, 1.7.0_06, 1.7.0_07, 1.7.0_08, 1.7.0_09, 1.7.0_10, 1.7.0_11, 1.7.0_12, 1.7.0_13, 1.7.0_14, 1.7.0_15, 1.7.0_17, 1.7.0_21, 1.7.0_25, 1.7.0_40, 1.7.0_45, 1.7.0_51, 1.7.0_55, 1.7.0_60, 1.7.0_65, 1.8.0_00, 1.8.0_05, 1.8.0_11, 1.8.0_20, 1.8.0_M6, 1.8.0_M7, 1.8.0_M8, 1.8.0_RC1, 1.8.0_25, 1.7.0_71, 1.8.0_31, 1.7.0_75, 1.8.
A few thoughts I had:
In the case of v3.7, should/can I update the {platform} to trusty as the version of memory-calculator appears to be present there?
Should I somehow downgrade the version of the memory-calculator used?
In the case of master, it appears that versions greater than 1.8.0_10+ exist in the repository index file. Since both of these issues are related to repositories and I haven't seen others post similar issues, could the root cause be coming from my vendor specific CF implementation? Its HPE Stackato.