Created attachment 1363579 [details] Screenshot when trying to enter CIDR Description of problem: Error Message during setup: The Engine VM (192.168.78.23) and this host (192.168.78.20/24) will not be in the same IP subnet. Root cause: The static ip address field during setup just allows to enter an ip address without CIDR (see attached screenshots). This value will be set as OVEHOSTED_VM/cloudinitVMStaticCIDR in the answer file. However OVEHOSTED_VM/cloudinitVMStaticCIDR expects to have a Version-Release number of selected component (if applicable): ovirt-node-ng-installer-master-2017120509.iso ovirt-engine-appliance-4.2-20171205.1.el7.centos.noarch.rpm How reproducible: Steps to Reproduce: 1. Install ovirt node cluster members 2. Start setup of hosted engine with gluster 3. Select to have a static ip for engine Actual results: OVEHOSTED_VM/cloudinitVMStaticCIDR missing CIDR Expected results: CIDR can be entered an will be set in answerfile Additional info: Workaround: Add CIDR notation in answerfile manually after setup failed and retry again.
Created attachment 1363580 [details] Screenshot only having address without CIDR
Please attach full setup logs. Thanks.
Simone explained the issue in private: The new cockpit plugin generates an answerfile with no CIDR. We have two options: 1. Move the bug there and add the CIDR 2. Change the code to add the CIDR if missing in answerfile. I think I'll opt for (2.). Logic will be same as today - use CIDR of the nic or bridge.
Created attachment 1363638 [details] Setup Log
Please note attachment
Option two might be a quick fix, due to the fact that some networks might use a different CIDR than /24.
*** Bug 1522941 has been marked as a duplicate of this bug. ***
Test versions: ovirt-node-ng-installer-master-2017121109 4.2.1-0.0.master.20171210113630.git504d08f.el7.centos Result: Works
Still being reproduced on these components: ovirt-hosted-engine-ha-2.2.5-1.el7ev.noarch ovirt-hosted-engine-setup-2.2.10-1.el7ev.noarch rhvm-appliance-4.2-20180202.0.el7.noarch Linux 3.10.0-693.19.1.el7.x86_64 #1 SMP Thu Feb 1 12:34:44 EST 2018 x86_64 x86_64 x86_64 GNU/Linux
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Created attachment 1397529 [details] Screenshot from 2018-02-18 13-00-19.png
I still see the same error as described within the attachment. cockpit-ovirt-dashboard-0.11.12-0.1.el7ev.noarch ovirt-hosted-engine-ha-2.2.6-1.el7ev.noarch ovirt-hosted-engine-setup-2.2.11-1.el7ev.noarch rhvm-appliance-4.2-20180202.0.el7.noarch Red Hat Enterprise Linux Server release 7.5 Beta (Maipo) Linux alma03.qa.lab.tlv.redhat.com 3.10.0-855.el7.x86_64 #1 SMP Tue Feb 20 06:46:45 EST 2018 x86_64 x86_64 x86_64 GNU/Linux Moving back to assigned. Happens on vintage and ansible.
Created attachment 1399505 [details] Screenshot from 2018-02-22 21-08-23.png
The fix is to consume host network mask length if we don't found a value in the answer file from cockpit vintage. If we also need to let the user enter a valid prefix from cockpit wizard please open a new bug there.
(In reply to Simone Tiraboschi from comment #15) > The fix is to consume host network mask length if we don't found a value in > the answer file from cockpit vintage. > > If we also need to let the user enter a valid prefix from cockpit wizard > please open a new bug there. So what will be the reproduction steps for this bug?
(In reply to Nikolai Sednev from comment #16) > So what will be the reproduction steps for this bug? Simply enter a static IPv4 address for the engine VM in cockpit, the engine VM will be configured with the host netmask.
(In reply to Simone Tiraboschi from comment #17) > (In reply to Nikolai Sednev from comment #16) > > So what will be the reproduction steps for this bug? > > Simply enter a static IPv4 address for the engine VM in cockpit, the engine > VM will be configured with the host netmask. But the static IP is not receiving the CIDR, e.g. x.x.x.x/y, it can only get static IP without CIDR, e.g. x.x.x.x. Wasn't this bug initially been open on CIDR inability of configuration from Cockpit UI? See also originally posted https://bugzilla.redhat.com/attachment.cgi?id=1363579.
(In reply to Simone Tiraboschi from comment #15) > The fix is to consume host network mask length if we don't found a value in > the answer file from cockpit vintage. > > If we also need to let the user enter a valid prefix from cockpit wizard > please open a new bug there. https://bugzilla.redhat.com/show_bug.cgi?id=1549983
Deployment of SHE Node 0, over NFS, using Cockpit, failed on these components: Works for me on these components on host: ovirt-hosted-engine-ha-2.2.7-1.el7ev.noarch ovirt-hosted-engine-setup-2.2.13-1.el7ev.noarch rhvm-appliance-4.2-20180202.0.el7.noarch Linux 3.10.0-861.el7.x86_64 #1 SMP Wed Mar 14 10:21:01 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 7.5 (Maipo) I've used static IP without CIDR prefix in Cockpit. [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: list object has no element 0\n\nThe error appears to have been in '/usr/share/ovirt-hosted-engine-setup/ansible/create_storage_domain.yml': line 111, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n - debug: var=app_ovf\n - name: parse OVF\n ^ here\n\nexception type: <class 'ansible.errors.AnsibleUndefinedVariable'>\nexception: list object has no element 0"}
Created attachment 1409549 [details] sosreport from alma04
(In reply to Nikolai Sednev from comment #20) > [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The task includes an > option with an undefined variable. The error was: list object has no element > 0\n\nThe error appears to have been in > '/usr/share/ovirt-hosted-engine-setup/ansible/create_storage_domain.yml': > line 111, column 5, but may\nbe elsewhere in the file depending on the exact > syntax problem.\n\nThe offending line appears to be:\n\n - debug: > var=app_ovf\n - name: parse OVF\n ^ here\n\nexception type: <class > 'ansible.errors.AnsibleUndefinedVariable'>\nexception: list object has no > element 0"} This really sounds like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1558036 Please retest this when 1558036 will be fixed.
Created attachment 1413011 [details] cockpit1
Created attachment 1413012 [details] cockpit2
Tested with these versions: rhvh-4.2.2.0-0.20180322.0+1 cockpit-ovirt-dashboard-0.11.19-1.el7ev.noarch ovirt-hosted-engine-setup-2.2.14-1.el7ev.noarch ovirt-hosted-engine-ha-2.2.7-1.el7ev.noarch rhvm-appliance-4.2-20180322.0.el7.noarch Test result: See the attachment 1413011 [details] and attachment 1413012 [details], it works well. So, I will change this bug's status to verified.
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 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.