On 03/06/2013 06:12 PM, Frederic Bevia wrote:
Sandro Bonazzola <sbonazzo@...> writes:
Hi Frederic, thanks for your report! ......;
Please run engine-cleanup, engine-setup and check ovirt-engine status if it fails again. If it fails, can you please attach your logs?
....> Regards, Sandro
Hi Sandro, thanks very much for your answer. I did run engine-cleanup, engine-setup and check ovirt-engine status and it failed again. But, meanwhile, to validate my hypothesis on the faulty name resolution, I installed dnsmasq, a small dns proxy/forwarder, on the same server (srv-santos.cg33.fr), wich can resolve name from local hosts file and from upstream DNS. Then, i re-run engine-setup, and bingo! :-)) no name résolution pbms and no error on JBoss.. Alas! it failed again shortly afterwards with this message: "could not create ovirtsdk API object" It seems to be a known bug cf. "https://bugzilla.redhat.com/show_bug.cgi?id=869457", fixed in lasts fedora's packages.. but apprently not in the ovirt-all-in-one packages on Centos 6. So unless if someone have a solution for this pbm, other than install ovirt on a fedora distrib with the last package of course, i just decided to stay on my centos 6, uninstall ovirt all-in-one and guive a try to a standard engine instal + a standard vdsm install on the same machine with the regular ovirt packages for centos.
Regards, Frederic
Hi Federic, if you just want to have a look at oVirt 3.2, get some experience with it or deploy it. you can try the ovirt-live image[1], just boot it up from a usb and you have oVirt 3.2 up and running. (based on fedora18) [1]http://wiki.ovirt.org/OVirt_Live
_______________________________________________ Users mailing list Users <at> ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users