Fix: Remove hosts file creation in sigul-install

Our Sigul bridges now have publicly accessible DNS names, so it is no
longer necessary to create an entry in the hosts file.

Issue: RELENG-4269
Change-Id: I8417747b598d4fad3bfef192ccf1056899ffdf0a
Signed-off-by: Eric Ball <eball@linuxfoundation.org>

diff --git a/releasenotes/notes/remove-sigul-hosts-file-7e665a543ae85ca3.yaml b/releasenotes/notes/remove-sigul-hosts-file-7e665a543ae85ca3.yaml
new file mode 100644 (file)
index 0000000..e15a785
--- /dev/null
+++ b/releasenotes/notes/remove-sigul-hosts-file-7e665a543ae85ca3.yaml
@@ -0,0 +1,7 @@
+---
+deprecations:
+  - |
+    Our Sigul bridges now have publicly accessible DNS names, so it is no longer
+    necessary to create an entry in the hosts file. Since this process relies
+    on up-to-date IP addresses being configured in each project's global env
+    vars, it can cause avoidable errors. It is therefore being removed.

diff --git a/shell/sigul-install.sh b/shell/sigul-install.sh
index 59d0a19..08b3b7d 100755 (executable)
--- a/shell/sigul-install.sh
+++ b/shell/sigul-install.sh
@@ -32,13 +32,3 @@ skip_if_unavailable=True" > fedora-infra-sigul.repo
     # install sigul
     sudo yum install -y -q sigul
 fi;
-# configure /etc/hosts with the sigul bridge hostname
-# This is needed as build minions can't always get DNS resolution
-# on the bridge
-BRIDGE_HOST=$(grep bridge-hostname "$SIGUL_CONFIG" | awk '{print $2}')
-
-# SIGUL_BRIDGE_IP must be defined as a Jenkins env variable
-cp /etc/hosts hosts
-echo -e "$SIGUL_BRIDGE_IP\t$BRIDGE_HOST" >> hosts
-sudo cp hosts /etc/hosts
-rm hosts