
Thanks, Didi! That really helped. I could not figure out what was getting parsed to set JAVA_HOME, thanks for indicating those scripts. In my environment there is a java-home.local; it pulls the home by running # exec java-config --select-vm=icedtea-7 --jre-home , which outputs a warning message because I have icedtea-bin-7 installed. I could change this script, or emerge icedtea-7 from sources (which is what I'll do, since I am not partial to binary builds). OVirt isn't in the main portage tree; I should contact the overlay maintainer to correct this script. Cheers, Carter Kindley Network Qualified Technician Deus Machine, LLC -----Original Message----- From: Yedidyah Bar David [mailto:didi@redhat.com] Sent: Monday, March 2, 2015 11:05 PM To: Carter Kindley Cc: users@ovirt.org Subject: Re: [ovirt-users] Ovirt engine-setup fails, "Cannot get JAVA_HOME" ----- Original Message -----
From: "Carter Kindley" <Carter.Kindley@deusmachine.com> To: users@ovirt.org Sent: Tuesday, March 3, 2015 3:06:44 AM Subject: [ovirt-users] Ovirt engine-setup fails, "Cannot get JAVA_HOME"
Hello folks,
After a long, long time compiling permutations, I went to finish setup of ovirt-engine on my Gentoo testbed. Running engine-setup, I receive an error after answering all prompts:
[ ERROR ] Failed to execute stage 'Setup validation': Cannot get JAVA_HOME ([u'\x1b[01m\x1b[31;06m!!! ERROR: The vm could not be found\x1b[0m'])
This machine has icedtea-bin-7.2.5.3, and # echo $JAVA_HOME yields /etc/java-config-2/current-system-vm which is linked to the icedtea-bin VM directory. Any thoughts to get me started?
The jre to use is determined by the script java-home (usually in /usr/share/ovirt-engine/bin, not sure about gentoo and/or your $PREFIX). IIRC only openjdk 1.7.0 is supported. If you look at this script, you see that if you put in its directory a script called java-home.local it will be called instead, thus letting you override that. Just add there a script outputting the JAVA_HOME you want and retry. Best, -- Didi This email has been scanned for viruses and private content. This message has been secured for compliance with the DM Cloud Mail Filter Service. For details on inbound and outbound filtering please contact your account specialist or primary technician.