From d3e188abf472c7e5fe70a36b5820fbffd9d32b8a Mon Sep 17 00:00:00 2001 From: Joseph Palermo Date: Mon, 15 Apr 2024 16:33:36 -0700 Subject: [PATCH] Fix gem bundle call during packaging We've seen some failures because it was simply using "bundle install" which does not properly install the gems into BOSH_INSTALL_TARGET. After upgrading to ruby 3.2 it seems that the gems instead are installed into /usr/local/bundle which does not transfer from the compilation VM into the package so when the CPI is later invoked the gems are missing. --- packages/bosh_aws_cpi/packaging | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/packages/bosh_aws_cpi/packaging b/packages/bosh_aws_cpi/packaging index 8c4dd0ac..7542e074 100644 --- a/packages/bosh_aws_cpi/packaging +++ b/packages/bosh_aws_cpi/packaging @@ -11,10 +11,6 @@ cp -a bosh_aws_cpi/* ${BOSH_INSTALL_TARGET} cd ${BOSH_INSTALL_TARGET} -export BUNDLER_VERSION="$(bundle -v | grep -o -e '[0-9.]*')" -bundle config set --local deployment 'true' -bundle config set --local no_prune 'true' -bundle config set --local without 'development test' bundle config set --local cache_path 'vendor/package' -bundle install +bosh_bundle_local