Description of problem: the hosted-engine wizard always forces he_host_ip to the value of ansible_default_ipv4 regardless of the interface choose by the user. ansible_default_ipv4 is always the IPv4 interface of the address with the IPv4 default route. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. deploy hosted-engine from cockpit 2. set the default route on a specific network interface of the host 3. deploy hosted-engine choosing a different interface fro the management network Actual results: The cockpit wizard always pass he_host_ip taking it from ansible_default_ipv4 regardless of the interface choose by the user. If VLANs are in place, the setup will choose the right id but then it will force the engine to connect the engine over a different interface failing the deployment with something like: 2019-01-29 16:40:19,494+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1) [19fd5ddb] EVENT_ID: VLAN_ID_MISMATCH_FOR_MANAGEMENT_NETWORK_CONFIGURATION(1,119), Failed to configure management network on host rhvh-01.lab.eng.tlv2.redhat.com. Host rhvh-01.lab.eng.tlv2.redhat.com has an interface bond0.200 for the management network configuration with VLAN-ID (200), which is different from data-center definition (201). Expected results: he_host_ip is not passed at all from the cockpit wizard since the ansible role is able to correctly fetch it according to the selected interface. Additional info:
Created attachment 1535148 [details] Log files
Created attachment 1535149 [details] Log files
Retest with redhat-virtualization-host-4.3-20190220.2.el7_6.x86_64.liveimg.squashfs, new bug 1679412 blocks this issue. When bug 1679412 fixed, QE will verify this bug.
Test Version rhvh-4.3.0.5-0.20190225.0+1 cockpit-system-176-4.el7.noarch cockpit-ws-176-4.el7.x86_64 cockpit-bridge-176-4.el7.x86_64 cockpit-storaged-176-4.el7.noarch cockpit-machines-ovirt-176-4.el7.noarch cockpit-176-4.el7.x86_64 cockpit-ovirt-dashboard-0.12.3-1.el7ev.noarch cockpit-dashboard-176-4.el7.x86_64 ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch ovirt-hosted-engine-setup-2.3.5-1.el7ev.noarch rhvm-appliance-4.3-20190220.2.el7.x86_64 Test Steps: 1. Clean install rhvh-4.3.0.5-0.20190225.0+1 2. Make the default route only on a specific network interface (em1) of the host 3. Deploy hosted engine with cockpit UI, choosing a different interface(em2) for the management network Result: Deploy failed at Prepare VM page, since "the resolved address doesn't resolve on the selected interface" change the status to "ASSIGNED"
Created attachment 1542042 [details] he_ssh_session logs
Created attachment 1543109 [details] Hang at "Obtain SSO token"
Retest with RHVH-4.3-20190313.3-RHVH-x86_64-dvd1.iso For cockpit user interface: Deployment failed since connection to em1 is broken. If restore the deployment from connecting to cockpit wizard via NIC em2, the deployment is blocked by the below bug https://bugzilla.redhat.com/show_bug.cgi?id=1422544 Test Version: RHVH-4.3-20190313.3-RHVH-x86_64-dvd1.iso cockpit-system-176-4.el7.noarch cockpit-ws-176-4.el7.x86_64 cockpit-bridge-176-4.el7.x86_64 cockpit-storaged-176-4.el7.noarch cockpit-ovirt-dashboard-0.12.5-1.el7ev.noarch cockpit-dashboard-176-4.el7.x86_64 cockpit-machines-ovirt-176-4.el7.noarch cockpit-176-4.el7.x86_64 ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch ovirt-hosted-engine-setup-2.3.6-1.el7ev.noarch rhvm-appliance-4.3-20190313.0.el7.x86_64 Test steps: According to comment 10 So the bug is blocked by BZ-1422544, QE cannot verify this issue until BZ-1422544 is fixed.
Discuss with simone, it is abnormal for em1 is broken in comment 12. So change the status to "ASSIGNED", and remove the depends bug.
Re-targeting to 4.3.3 having failed QA on 4.3.2
Moving back to ON_QA, please retest once https://bugzilla.redhat.com/show_bug.cgi?id=1693560 is fixed.
The test machine need to be set to use the binded VMs for hosted engine testing. The ticket to IT has been sent out. https://redhat.service-now.com/surl.do?n=PNT0520276 I will verify this bug until the ticket is fixed.
Test Version RHVH-4.3-20190404.1-RHVH-x86_64-dvd1.iso cockpit-system-176-4.el7.noarch cockpit-ws-176-4.el7.x86_64 cockpit-bridge-176-4.el7.x86_64 cockpit-storaged-176-4.el7.noarch cockpit-ovirt-dashboard-0.12.7-1.el7ev.noarch cockpit-machines-ovirt-176-4.el7.noarch cockpit-dashboard-176-4.el7.x86_64 cockpit-176-4.el7.x86_64 ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch ovirt-hosted-engine-setup-2.3.7-1.el7ev.noarch rhvm-appliance-4.3-20190404.1.el7.x86_64 Test Steps: 1. Clean install RHVH-4.3-20190404.1-RHVH-x86_64-dvd1.iso (nics em1 and em2) 2. Make the default gateway on em2 prioritized 3. Deploy hosted engine with "bridge interface"="em2" setting via cockpit. Result: Hosted engine deploys successfully. Bug is fixed, move it to "VERIFIED" stirabos, Thank you so much for giving the points of the testing.
This bugzilla is included in oVirt 4.3.4 release, published on June 11th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.4 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.