On Sun, Dec 18, 2016 at 11:32 PM, Mark Steckel <mjs@fix.net> wrote:
Still trying to get a single server hosted engine setup running at Hetzner.de...

If I use the HE Appliance and do not use cloud-init the VM launches but can not be accessed.

<quote>
[ INFO  ] Detecting available oVirt engine appliances
          The following appliance have been found on your system:
                [1] - The oVirt Engine Appliance image (OVA) - 4.0-20161210.1.el7.centos
                [2] - Directly select an OVA file
          Please select an appliance (1, 2) [1]: 1
[ INFO  ] Verifying its sha1sum
[ INFO  ] Checking OVF archive content (could take a few minutes depending on archive size)
[ INFO  ] Checking OVF XML content (could take a few minutes depending on archive size)
[WARNING] OVF does not contain a valid image description, using default.
          Would you like to use cloud-init to customize the appliance on the first boot (Yes, No)[Yes]? No
[WARNING] The oVirt engine appliance is not configured with a default password, please consider configuring it via cloud-init

<snip...>

          Make a selection from the options below:
          (1) Continue setup - oVirt-Engine installation is ready and ovirt-engine service is up
          (2) Abort setup
          (3) Power off and restart the VM
          (4) Destroy VM and abort setup

</quote>

At this point I can access the VM via vnc but am unable to login.

Is root login possible in this situation?

Hi Mark,
there is no default password in the appliance so you have to configure it via cloud-init or to manually force from the emergency mode.

If you are going to use cloud-init you could just decide to set the VM name and the root password without automatically executing engine-setup there.
Can I ask why you want to avoid cloud-init?

thanks,
Simone




_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users