chef S390x testers failing on bundler https error Ruby

Bundler version 2.2.15

RSpec 3.10

  - rspec-core 3.10.1

  - rspec-expectations 3.10.1

  - rspec-mocks 3.10.2

  - rspec-support 3.10.2

Defaults:jenkins !secure_path, exempt_group += jenkins

Don't run Bundler as root. Bundler can ask for sudo if it is needed, and

installing your bundle as root will break this application for all non-root

users on this machine.

Fetching source index from https://rubygems.org/



Retrying fetcher due to error (2/4): Bundler::Fetcher::CertificateFailureError Could not verify the SSL certificate for https://rubygems.org/.

There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification. For information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.



Retrying fetcher due to error (3/4): Bundler::Fetcher::CertificateFailureError Could not verify the SSL certificate for https://rubygems.org/.

There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification. For information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.



Retrying fetcher due to error (4/4): Bundler::Fetcher::CertificateFailureError Could not verify the SSL certificate for https://rubygems.org/.

There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification. For information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.



Could not verify the SSL certificate for https://rubygems.org/.

There is a chance you are experiencing a man-in-the-middle attack, but most

likely your system doesn't have the CA certificates needed for verification. For

information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect

without using SSL, edit your Gemfile sources and change 'https' to 'http'.

🚨 Error: The command exited with status 17
^^^ +++
^^^ +++
~~~ Running plugin omnibus post-command hook
$ /var/lib/buildkite-agent/plugins/github-com-chef-omnibus-buildkite-plugin-v0-2-16/hooks/post-command
~~~ Running global pre-exit hook
$ /etc/buildkite-agent/hooks/pre-exit
~~~ Running plugin omnibus pre-exit hook
$ /var/lib/buildkite-agent/plugins/github-com-chef-omnibus-buildkite-plugin-v0-2-16/hooks/pre-exit

https://buildkite.com/chef/chef-chef-master-omnibus-release/builds/1185#d98c91b3-66f5-4d6b-acd1-7da10691945f

Asked Oct 07 '21 03:10
avatar tas50
tas50

1 Answer:

The el-8 and sles-15 s390x hosts have an entry in /etc/hosts/ for rubygems.org because for some reason bundler can't resolve an IP address without it. Apparently rubygems.org recently changed its IP address which caused bundler failures. Once I updated the /etc/hosts entry with the correct IP address bundler started working correctly.

1 hour release engineering time spent on this issue.

1
Answered Apr 22 '21 at 19:28
avatar  of jeremiahsnapp
jeremiahsnapp