Description of problem: Error while deploying Hosted-engine vi cockpit with NFS: [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'STORAGE_DOMAIN_ADDR' is undefined\n\nThe error appears to have been in '/usr/share/ovirt-hosted-engine-setup/ansible/create_storage_domain.yml': line 32, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n set_fact: datacenter_name={{ ovirt_datac enters|json_query(\"[?id=='\" + datacenter_id + \"'].name\")|first }}\n - name: Add nfs storage domain\n ^ here\n\nexception type: <class 'ansible.errors.AnsibleUndefinedVariable'>\nexception: 'STORAGE_DOMAIN_ADDR' is undefined"} How reproducible: 100% Steps to Reproduce: 1. run Hosted-Engine deployment via cockpit with default values 2. choose NFS 3. The error appears Actual results: Error appears Expected results: Successful deployment Additional info: cockpit-ovirt-dashboard-0.11.16-1
Tested with 11.16, can reproduce this issue.
Tested with 11.19, deploy HE with NFS storage via cockpit successfully. [root@ibm-x3650m5-06 ~]# hosted-engine --vm-status --== Host 1 status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : ibm-x3650m5-06.lab.eng.pek2.redhat.com Host ID : 1 Engine status : {"health": "good", "vm": "up", "detail": "Up"} Score : 3400 stopped : False Local maintenance : False crc32 : 004d9896 local_conf_timestamp : 141678 Host timestamp : 141678 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=141678 (Mon Mar 26 11:37:08 2018) host-id=1 score=3400 vm_conf_refresh_time=141678 (Mon Mar 26 11:37:08 2018) conf_on_shared_storage=True maintenance=False state=EngineUp stopped=False 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.