[Users] Failing on new setup

[Jaco]

Thank you for the feedback, guys.

I've slogged away at it a bit one more, doing an engine-clean & 
referencing this setup-guide:
http://blog.jebpages.com/archives/up-and-running-with-ovirt-3-2-edition/

I'm not sure what the functional differences were from my previous setup 
(maybe some dependencies provided by the all-in-1?), but I'm able to 
associate a HV host now & provision instances :)

I've also, prior to the above, encountered issues with vdsm that 
resolved itself.

#systemctl status vdsmd.service
vdsmd.service - Virtual Desktop Server Manager
       Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled)
       Active: failed (Result: exit-code) since Mon 2013-02-18 13:46:03 
NZDT; 7s ago
      Process: 24727 ExecStart=/lib/systemd/systemd-vdsmd start 
(code=exited, status=1/FAILURE)
     Main PID: 1367 (code=killed, signal=TERM)
       CGroup: name=systemd:/system/vdsmd.service

Feb 18 13:46:02 tin.we.gen.nz python[24860]: DIGEST-MD5 client step 2
Feb 18 13:46:02 tin.we.gen.nz python[24860]: DIGEST-MD5 client step 2
Feb 18 13:46:02 tin.we.gen.nz python[24860]: DIGEST-MD5 client step 3
Feb 18 13:46:03 tin.we.gen.nz systemd-vdsmd[24727]: conflicting vdsm and 
libvirt-qemu tls configuration.
Feb 18 13:46:03 tin.we.gen.nz systemd-vdsmd[24727]: vdsm.conf with 
ssl=False requires the following changed:
Feb 18 13:46:03 tin.we.gen.nz systemd-vdsmd[24727]: libvirtd.conf: 
listen_tcp=1, auth_tcp="none",
Feb 18 13:46:03 tin.we.gen.nz systemd-vdsmd[24727]: qemu.conf: spice_tls=0.
Feb 18 13:46:03 tin.we.gen.nz systemd[1]: vdsmd.service: control process 
exited, code=exited status=1
Feb 18 13:46:03 tin.we.gen.nz systemd[1]: Failed to start Virtual 
Desktop Server Manager.
Feb 18 13:46:03 tin.we.gen.nz systemd[1]: Unit vdsmd.service entered 
failed state

I've made changes to vdsm.conf, libvirtd.conf & qemu.conf to not make 
use of TLS.

So, for now, I have a functional host, at the expense of robust security.

This is still a PoC box, so I'll have to go though the whole exercise 
again, and may be able to furnish you with the logs & other data you've 
requested.

I believe this box is an oVirt, but future HV nodes will probably be set 
using the oVirt-node liveCD ISO (?)

Thanks for a *great* product!
I find it to be superior to OpenStack (too admin-overhead heavy) & 
CloudStack (immature; lack fine-grain controls needed)

- J


On 13/2/18 18:04 , Vered Volansky wrote:
> Hi Jaco,
>
> Are you using ovirt-node or ovirt?
> What is the status of your host?
> What about vdsmd service on your host? is it running?
> What do you get if you try to run VdsClient on your host (command line)?
>
> Also - please send full engine and vdsm logs, it can always give us more insight and expedite issues resolution.
>
> Best Regards,
> Vered
>
> ----- Original Message -----
>> From: "Jaco" <ubuntumuntu at gmail.com>
>> To: users at ovirt.org
>> Sent: Monday, February 18, 2013 1:11:16 AM
>> Subject: [Users] Failing on new setup
>>
>>
>> Hi guys,
>>
>> New to oVirt - and "new" to Fedora after a *very long* break @ using
>> Debian/Ubuntu almost exclusively for the last few years.
>> Much has changed, so please pardon my ignorance - got some
>> catching-up to do.
>>
>> I'm doing PoC of a number of systems, so need to give oVirt a fair
>> shake, but I'm tripping up before I can even get going (does not
>> bode well).
>>
>> I've tried following the QuickStart, all-in-one & other guides, &
>> quickly came across issues.
>> Next I'll have to start building from source - a prospect that will
>> by no means present me with less issues.
>>
>> New F18, minimal headless server.
>>
>> Installed via yum as documented, but install failed at the last
>> steps, as there seems to be an issue with the scripts'
>> implementation of firewalld.
>> A very nice chap @ the IRC channel managed to help be out to get over
>> that initial hurdle - had to *completely* disable firewalld & select
>> the 'None' option for the setup. (seems like a really bad idea to
>> start off like that - disabling security - but this is a lab PoC, so
>> OK, will let it slide for now)
>> I've also disabled SELinux & IPtables via systemctl - so that we can
>> eliminate that as an issue.
>>
>> Script(s) still don't complete without issue, but at lease the engine
>> seems to come up & I can log in.
>>
>> After logging in, I try to (re)connect to the local hypervisor via
>> (root@) $FQDN, localhost & 127.0.0.1, but it fails to come up (why
>> root? OK....).
>> It adds the host, but there seems to be connectivity issues.
>>
>> I'm seeing this in the GUI events:
>> Host localhost installation failed. Command returned failure code 1
>> during SSH session 'root at localhost'.
>>
>> I'm seeing this in `tail -f /var/log/ovirt-engine/engine.log`
>> http://pastebin.com/nVyNGSsf
>> Relevant line being:
>> ERROR [org.ovirt.engine.core.utils.ssh.SSHDialog] (pool-3-thread-31)
>> SSH error running command root at localhost:'umask 0077;
>> MYTMP="$(mktemp -t ovirt-XXXXXXXXXX)"; trap "chmod -R u+rwX
>> \"${MYTMP}\" > /dev/null 2>&1; rm -fr \"${MYTMP}\" > /dev/null 2>&1"
>> 0; rm -fr "${MYTMP}" && mkdir "${MYTMP}" && tar -C "${MYTMP}" -x &&
>> "${MYTMP}"/setup DIALOG/dialect=str:machine
>> DIALOG/customization=bool:True': java.io.IOException: Command
>> returned failure code 1 during SSH session 'root at localhost'
>>
>> This is a *fresh* box - I've reinstalled it a few times from scratch
>> now - & I've re-installed oVirt through the manners documented, but
>> I'm not getting anywhere fast.
>> In this, google is not my friend, as results are sparse & not very
>> helpful - i.e. if someone's found resolution, it has not been
>> posted.
>>
>> Either there's a bug in the docco's or the code/scripts.
>>
>> Please help - I'd *really* like to give this a go
>>
>> Kind regards
>>
>> -Jaco
>>
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>