summaryrefslogtreecommitdiffstats
path: root/apex/network/network_data.py
diff options
context:
space:
mode:
authorTim Rozet <trozet@redhat.com>2019-01-04 12:28:30 -0500
committerTim Rozet <trozet@redhat.com>2019-01-11 15:52:51 -0500
commit4cbad53ea9293fd51c5ffc368ca01787549472f7 (patch)
treeb7d15482235035f91d7ebc025563de8c4350aac6 /apex/network/network_data.py
parente1c6f92cdac07949b00c758bab5c79ff20639dd9 (diff)
Fixes undercloud install failure with setting hostname
There is a new bug when deploying master/rocky where the OS of the undercloud/overcloud is now upgraded to CentOS 7.6. When the undercloud install runs it fails to configure the hostname using hostnamectl. This is because systemd-hostnamed is not running and fails to start. Simply reloading dbus seems to fix the issue. In the dbus logs there are odd error messages like: dbus-daemon[3230]: Unknown username "root" in message bus configuration file Disabling selinux seems to fix this. This patch also moves to use podman instead of docker for container management and invokes a script in Ansible which updates NIC templates as new variables are added upstream. Furthermore, with the new patches for routed networks in OOO, it is now required that the MTU is set in network-data, as well as adding the External network to the Compute role. Now the External network is removed by default from the Compute role. Change-Id: Ie8b86f6f28d69bda11b1f7a430df882970ac3cb9 Signed-off-by: Tim Rozet <trozet@redhat.com>
Diffstat (limited to 'apex/network/network_data.py')
-rw-r--r--apex/network/network_data.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/apex/network/network_data.py b/apex/network/network_data.py
index 1177af0..6f330c5 100644
--- a/apex/network/network_data.py
+++ b/apex/network/network_data.py
@@ -83,7 +83,7 @@ def create_network_data(ns, target=None):
"{}".format(net))
raise NetworkDataException("cidr is null for network {}".format(
net))
-
+ tmp_net['mtu'] = network.get('mtu', 1500)
network_data.append(copy.deepcopy(tmp_net))
# have to do this due to the aforementioned bug