Bug 1556866
| Summary: | The deployment fails on create_storage_domain stage | ||
|---|---|---|---|
| Product: | [oVirt] cockpit-ovirt | Reporter: | Simone Tiraboschi <stirabos> |
| Component: | Hosted Engine | Assignee: | Simone Tiraboschi <stirabos> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Yihui Zhao <yzhao> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 0.11.17 | CC: | bugs, cshao, huzhao, qiyuan, rbarry, sbonazzo, stirabos, yaniwang, ycui, ykaul, yzhao |
| Target Milestone: | ovirt-4.2.2 | Keywords: | Regression |
| Target Release: | --- | Flags: | rule-engine:
ovirt-4.2+
rule-engine: blocker+ yzhao: testing_ack+ |
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | cockpit-ovirt-0.11.18-0.1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-03-29 11:20:26 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1558036 | ||
| Bug Blocks: | 1540621, 1555365, 1557480 | ||
*** Bug 1556885 has been marked as a duplicate of this bug. *** QE can reproduce this issue.
Test version:
cockpit-dashboard-160-3.el7.x86_64
cockpit-system-160-3.el7.noarch
cockpit-ovirt-dashboard-0.11.17-1.el7ev.noarch
cockpit-bridge-160-3.el7.x86_64
cockpit-ws-160-3.el7.x86_64
cockpit-storaged-160-3.el7.noarch
cockpit-160-3.el7.x86_64
ovirt-hosted-engine-ha-2.2.7-1.el7ev.noarch
ovirt-hosted-engine-setup-2.2.13-1.el7ev.noarch
vdsm-http-4.20.22-1.el7ev.noarch
vdsm-hook-ethtool-options-4.20.22-1.el7ev.noarch
vdsm-network-4.20.22-1.el7ev.x86_64
vdsm-api-4.20.22-1.el7ev.noarch
vdsm-python-4.20.22-1.el7ev.noarch
vdsm-hook-vmfex-dev-4.20.22-1.el7ev.noarch
vdsm-hook-vhostmd-4.20.22-1.el7ev.noarch
vdsm-yajsonrpc-4.20.22-1.el7ev.noarch
vdsm-client-4.20.22-1.el7ev.noarch
vdsm-4.20.22-1.el7ev.x86_64
vdsm-gluster-4.20.22-1.el7ev.noarch
vdsm-hook-vfio-mdev-4.20.22-1.el7ev.noarch
vdsm-common-4.20.22-1.el7ev.noarch
vdsm-hook-openstacknet-4.20.22-1.el7ev.noarch
vdsm-jsonrpc-4.20.22-1.el7ev.noarch
vdsm-hook-fcoe-4.20.22-1.el7ev.noarch
rhvm-appliance-4.2-20180202.0.el7.noarch
rhvh-4.2.1.4-0.20180305.0+1
Test result:
[ INFO ] TASK [parse OVF]
[ 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"}
LOCAL_VM_DIR got passed but with a wrong value [root@c74he20180302h1 ~]# cat /var/lib/ovirt-hosted-engine-setup/cockpit/ansibleVar* LOCAL_VM_DIR: localvm Could we build the build in brew to QE with this bug fix to unblock the testing for bugs 1528134 1539560 1540621 1555365 1557480 asap? We have https://bugzilla.redhat.com/show_bug.cgi?id=1558036 which is still on POST and can cause many different side effects. I'd suggest to rebuild once we have a valid fix for 1558036. 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 Tested results: from the cockpit: """ [ INFO ] TASK [Get Cluster CPU model] [ INFO ] ok: [localhost] [ INFO ] TASK [Get storage domain details] [ INFO ] ok: [localhost] [ INFO ] TASK [Add HE disks] [ INFO ] TASK [Register disk details] [ INFO ] ok: [localhost] [ INFO ] TASK [Add VM] [ INFO ] changed: [localhost] """ Create storage domain task works well. So, 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. |
Description of problem: seen choosing NFS, version=auto The deployment fails with: [ INFO ] TASK [Find the appliance OVF] [ INFO ] TASK [parse OVF] [ 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"} I think that the issue is that LOCAL_VM_DIR is not passed to create_storage_domain.yml It has to be passed to create_target_vm.yml as well Version-Release number of selected component (if applicable): cockpit-ovirt-dashboard.noarch 0.11.17-1.el7.centos How reproducible: 100% Steps to Reproduce: 1. try deploying hosted-engine from cockpit 2. 3. Actual results: It fails with: [ INFO ] TASK [Find the appliance OVF] [ INFO ] TASK [parse OVF] [ 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"} Expected results: Successful deployment Additional info: It correctly works on CLI