Description of problem: Attaching an answer file to 'hosted-engine --deploy --config-append=<path>' does not work when the <path> starts with '~/' Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: run hosted-engine --deploy --config-append=<path that starts with ~/> i.e: run hosted-engine --deploy --config-append=~/answers.conf Actual results: answerfile was not found Expected results: answer file should be found and read Additional info: [root@host1 ~]# hosted-engine --deploy --config-append=~/hosted-engine-answers.conf [ INFO ] Stage: Initializing [ INFO ] Generating a temporary VNC password. [ INFO ] Stage: Environment setup During customization use CTRL-D to abort. Continuing will configure this host for serving as hypervisor and create a VM where you have to install the engine afterwards. Are you sure you want to continue? (Yes, No)[Yes]: It has been detected that this program is executed through an SSH connection without using screen. Continuing with the installation may lead to broken installation if the network connection fails. It is highly recommended to abort the installation and run it inside a screen session using command "screen". Do you want to continue anyway? (Yes, No)[No]: yes [ INFO ] Hardware supports virtualization Configuration files: [] [WARNING] The following configuration files are missing: ~/hosted-engine-answers.conf. Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20171228041706-mpmd38.log Version: otopi-1.7.6_master (otopi-1.7.6-0.0.master.20171204131110.gitd5016f6.el7.centos) [ INFO ] Detecting available oVirt engine appliances [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup
Works for me on these components: rhvm-appliance-4.2-20180202.0.el7.noarch ovirt-hosted-engine-ha-2.2.4-1.el7ev.noarch ovirt-hosted-engine-setup-2.2.9-1.el7ev.noarch Linux 3.10.0-693.17.1.el7.x86_64 #1 SMP Sun Jan 14 10:36:03 EST 2018 x86_64 x86_64 x86_64 GNU/Linux Moving to verified.
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 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.