Unsupported bundler version for v3/buildpacks

[renelehmann]

Environment: Using cats v7.3.0 Using current ruby buildpack v1.8.50 (https://github.com/cloudfoundry/ruby-buildpack/releases/tag/v1.8.50) (Using cf-deployment 17.1.0 with latest buildpack releases)

Failure: cats test v3/buildpacks "Stages with multiple admin buildpacks" fails because of the unsupported bundler version used on the lockfile and since the update of ruby buildpack from v1.8.49 to v1.8.50.

Staging failure (snipped):

   2022-01-11T11:22:15.91+0000 [STG/0] OUT        Installing bundler 1.14.6
   2022-01-11T11:22:16.43+0000 [STG/0] ERR        /tmp/contents1479471521/deps/0/ruby/lib/ruby/site_ruby/2.7.0/rubygems.rb:836: warning: __FILE__ in eval may not return location
in binding; use Binding#source_location instead
   2022-01-11T11:22:16.43+0000 [STG/0] ERR        /tmp/contents1479471521/deps/0/vendor_bundle/ruby/2.7.0/gems/bundler-1.14.6/lib/bundler/rubygems_integration.rb:516: warning: in
 `eval'
   2022-01-11T11:22:16.58+0000 [STG/0] OUT        The Gemfile specifies no dependencies
   2022-01-11T11:22:16.58+0000 [STG/0] OUT        Bundle complete! 0 Gemfile dependencies, 1 gem now installed.
   2022-01-11T11:22:16.58+0000 [STG/0] OUT        Gems in the groups development and test were not installed.
   2022-01-11T11:22:16.59+0000 [STG/0] OUT        Bundled gems are installed into /tmp/contents1479471521/deps/0/vendor_bundle.
   2022-01-11T11:22:16.92+0000 [STG/0] OUT        **ERROR** Unable to install gems: exit status 15
   2022-01-11T11:22:17.14+0000 [STG/0] ERR Failed to run all supply scripts: exit status 15
   2022-01-11T11:22:17.15+0000 [STG/0] OUT Exit status 225
   2022-01-11T11:22:17.48+0000 [STG/0] OUT Cell 87f0f175-4085-4123-946e-cc9eb12085b8 stopping instance 57e61156-e415-4a42-b075-951a8dc9cee4
   2022-01-11T11:22:17.48+0000 [STG/0] OUT Cell 87f0f175-4085-4123-946e-cc9eb12085b8 destroying container for instance 57e61156-e415-4a42-b075-951a8dc9cee4
   2022-01-11T11:22:17.57+0000 [API/0] ERR Failed to stage build: staging failed

Referred test: https://github.com/cloudfoundry/cf-acceptance-tests/blob/72bc3239f222dba27a3a8e6cf2a8141c7a7b84ee/v3/buildpacks.go#L116

Uploaded package with Gemfile.lock: https://github.com/cloudfoundry/cf-acceptance-tests/blob/v7.3.0/assets/go_calls_ruby.zip "BUNDLED WITH 1.14.6"

cats v7.3.0 works with ruby buildpack v1.8.49 (as tested with cf-deployment v17.1.0)

[ctlong]

✅ Thanks for bringing this up @renelehmann

🔬 I'm investigating right now

[ctlong]

🕵️ assets/go_calls_ruby.zip is out of date assets/go_calls_ruby was updated more recently than assets/go_calls_ruby.zip specifically to not have to worry about bundler versions. Re-zipping assets/go_calls_ruby to assets/go_calls_ruby.zip with zip -r go_calls_ruby.rb go_calls_ruby and re-running CATS appears to fix the ruby_buildpack issues.

😕 zipped go apps are failing to start After resolving the ruby_buildpack error another error was exposed appearing to relate to the go_buildpack. I made a new Github issue encapsulating the problem.

[ctlong]

We think that we've resolved the issue. The fix is running through the pipeline now.

[ctlong]

🎉 Resolved