The script that fixes the problem that occurs after ECE 1.0.x is upgraded to 1.1.0.

fix-service-forwarder.sh

#!/bin/bash
#The script fixes the problem that occurs after ECE 1.0.x is upgraded to 1.1.0. 
# 1. Make sure that 'jq' is installed on the host where you will run the script.
# 2. Change variables below.
#    NODE_IP - IP address of the coordinator
#    AUTH - credentials to access adminconsole. Use `root` user only
# 3. Run script
# 4. Remove service `frc-services-forwarders-services-forwarder` on every ECE host. The runner should re-create it immediately.
# 5. Check that the service is running.

# 0] Environment
#Coordinator IP address
export NODE_IP="192.168.44.10"
export URI_PREFIX="$NODE_IP:12400"
export AUTH="root:test"

# 1] Get service-forwarder config and add extra host
export UPDATED_CONTAINER=$(curl -u "$AUTH" "$URI_PREFIX/api/v0/regions/ece-region/container-sets/services-forwarders" | jq '.containers["services-forwarder"].data' | sed s/'"ExtraHosts": \[\]'/'"ExtraHosts": ["containerhost:${RUNNER_HOST_IP}"]'/)
# 2] Push container configuration back
curl -u "$AUTH" -X POST "$URI_PREFIX/api/v0/regions/ece-region/container-sets/services-forwarders/containers/services-forwarder" -d "$UPDATED_CONTAINER"

echo -e "\n\e[33mPlease execute 'docker rm -f frc-services-forwarders-services-forwarder' on every host that runs ECE\e[0m"