+++ This bug is an upstream to downstream clone. The original bug is: +++ +++ bug 1492791 +++ ====================================================================== Description of problem: Due to an upstream cloud-init bug ( https://bugs.launchpad.net/cloud-init/+bug/1686856 ), the default gateway is not configured on the Engine VM if deployed with static IP. It affects RHEL 7.4 and Centos 7.4 (used as the base of the engine-appliance, not related to host OS). Version-Release number of selected component (if applicable): The issue is cloud-init on the engine VM OS: 7.4 How reproducible: 100% Steps to Reproduce: 1. deploy hosted-engine with static IP for the engine VM 2. 3. Actual results: The engine VM has no gateway and so no network connectivity Expected results: The default gateway on the engine VM is correctly configured Additional info: It affects RHEL 7.4 and Centos 7.4 (used as the base of the engine-appliance, not related to host OS) (Originally by Simone Tiraboschi)
Not depending on bug #1492726 since we can workaround it. Moved bug #1492726 to see also. (Originally by Sandro Bonazzola)
*** Bug 1493070 has been marked as a duplicate of this bug. *** (Originally by didi)
Successfully deployed ovirt-hosted-engine-setup-2.1.4-1.el7ev.noarch with rhvm-appliance-4.1.20170914.0-1.el7.noarch and ovirt-engine-setup-4.1.6.2-0.1.el7.noarch inside, on RHEL7.4, using static IP configuration on SHE-VM, did not seen any default gateway issues with the deployment. Moving to verified.
SHE-VM with static ip deployed successfully. Test version: rhvh-4.1-0.20170925.0+1 ovirt-hosted-engine-setup-2.1.3.9-1.el7ev.noarch cockpit-ovirt-dashboard-0.10.8-2.2.ovirt41.el7ev.noarch rhvm-appliance-4.1.20170914.0-1.el7.noarch ovirt-host-deploy-1.6.6-1.el7ev.noarch Steps: 1. deploy hosted-engine with static IP for the engine VM Result: Deploy successfully and didn't see any default gateway issues with the deployment.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2807