Re: [Users] [ovirt-test-day-2] Testing all-in-one feature on f19

----- Original Message ----- > From: "Karli Sjöberg" <Karli.Sjoberg(a)slu.se&gt; > To: didi(a)redhat.com > Cc: iheim(a)redhat.com, users(a)ovirt.org > Sent: Wednesday, February 12, 2014 12:34:18 PM > Subject: Re: [Users] [ovirt-test-day-2] Testing all-in-one feature on f19 > > On Wed, 2014-02-12 at 05:09 -0500, Yedidyah Bar David wrote: > > ----- Original Message ----- > > > From: "Karli Sjöberg" <Karli.Sjoberg(a)slu.se&gt; > > > To: didi(a)redhat.com > > > Cc: iheim(a)redhat.com, users(a)ovirt.org > > > Sent: Wednesday, February 12, 2014 11:52:55 AM > > > Subject: Re: [Users] [ovirt-test-day-2] Testing all-in-one feature on f19 > > > > > > > > > > > > > > Oh, and we tried using the "ovirt-log-collector" to compile the > > > > > > > logs > > > > > > > but > > > > > > > it failed when trying to gather hypervisor data, just after we > > > > > > > typed > > > > > > > in > > > > > > > the password for "admin@internal". Even when executing with the > > > > > > > option > > > > > > > "--no-hypervisors" it still tried to do that?! > > > > > > > > > > > > I think it should work. Can you send logs please? > > > > > > > > > > Does the log-collector log it´s own logging?:) Or what logs are you > > > > > referring to? > > > > > > > > Sorry for being unclear. > > > > > > > > Output of the command, preferably with --verbose > > > > (--log-file does write to a log, btw...). > > > > > > > > Thanks. > > > > -- > > > > Didi > > > > > > Here you are: > > > > > > http://pastebin.com/Hwya90LF > > > > Sorry, I meant with '--no-hypervisors'... > > > > The actual bug you encountered seems to be solved by [1]. > > > > [1] http://gerrit.ovirt.org/23488 > > -- > > Didi > > Huh, that´s so strange, it worked this time with "--no-hypervisors": > http://pastebin.com/2RSjsT2i > > This time it outputs correctly and also running without "--verbose" > produces an expected output. But the first time we ran it, even with > "--no-hypervisors", both me and my colleague remember it like it bombed > out and didn´t print out the last lines about where it collected and > placed the archive and such. Definitely not something you´d take for > successful at least. OK, but did it fail during trying to connect to the engine to get the list of hypervisors? Perhaps there was some other problem?

> > But now it works, tested a couple of times just to be sure... False > alarm... OK... Thanks for the report! -- Didi