On ubuntu, run the following command:
sudo service haproxy status
You should see output like below if it is running:
haproxy is running.
| Content-Type: multipart/mixed; boundary="===============0035287898381899620==" | |
| MIME-Version: 1.0 | |
| --===============0035287898381899620== | |
| Content-Type: text/cloud-config; charset="us-ascii" | |
| MIME-Version: 1.0 | |
| Content-Transfer-Encoding: 7bit | |
| Content-Disposition: attachment; filename="cloud-config.txt" | |
| #cloud-config |
| #!/bin/bash | |
| # Install pre-requisites | |
| apt-get install software-properties-common | |
| # Add PPAs | |
| apt-add-repository ppa:brightbox/ruby-ng -y | |
| apt-add-repository ppa:ansible/ansible -y | |
| # Run update |
| # !/bin/bash | |
| # Script to use Fleetctl to stop and start containers using a rolling restart | |
| # By Troy Fontaine with rolling restart script from http://engineering.rainchasers.com/coreos/fleet/2015/03/03/rolling-unit-restart.html | |
| # Grab list of containers and assign to array | |
| container_list=($(fleetctl list-units -fields=unit -no-legend | cut -f2 )) | |
| # Prepare variable for later use | |
| container="" |
Based on the work by wjordan in this comment
The solution is to force the update of RubyGems to side step the issue.
gem update --force --system 2.6.11
Then the error does not occur.