+++ This bug was initially created as a clone of Bug #1553758 +++ --- Additional comment from Steve Goodman on 2019-04-01 06:39:19 UTC --- Sandro, As a newcomer to RHV, I found the whole concept of the appliance to be very confusing. When I looked up what an appliance is, I found that it's a self-contained virtual machine used for a specific purpose. However, the way we use the term in the documentation, it is only for installing the virtual machine that hosts the engine, not the virtual machine itself. BUT we use the term inconsistently, which leads to more confusion. Specifically: * We use the term in the documentation, as I just mentioned, to refer to something that installs the virtual machine that hosts the engine. * But in the current SHE Guide, in section 2.2, step 7 [1], the command prompt refers to the appliance as the actual virtual machine, not just something used to install the vm: > Please provide the FQDN you would like to use for the engine appliance. > Note: This will be the FQDN of the engine VM you are now going to launch, > it should not point to the base host or to any other existing machine. > Engine VM FQDN: manager.example.com > Please provide the domain name you would like to use for the engine appliance. > Engine VM domain: [example.com] [1] https://access.redhat.com/documentation/en-aus/red_hat_virtualization/4.2/html-single/self-hosted_engine_guide/#Deploying_the_Self-Hosted_Engine_Using_the_CLI_deploy The command prompts and the documentation need to be in sync. The command prompts should be updated.
I see that this was given the keyword Documentation. This is not a documentation bug. It is a bug in the text in the installer script. I'm not sure what the correct keyword is, but I don't think it's "Documentation".
Works for me on these components: ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch ovirt-hosted-engine-setup-2.3.9-1.el7ev.noarch [ INFO ] Detecting host timezone. Please provide the FQDN you would like to use for the engine. Note: This will be the FQDN of the engine VM you are now going to launch, it should not point to the base host or to any other existing machine. Engine VM FQDN: []:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:1563