4:36 a.m.
Hi,
any idea on why http://jenkins.ovirt.org/job/ovirt_engine_3.3_find_bugs_gerrit/5094 is
failing?
It's totally unrelated to the change, it seems to be something wrong in the
environment configuration:
Error: JAVA_HOME is not defined correctly.
We cannot execute /usr/lib/jvm/java-1.7.0-openjdk.x86_64/bin/java
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10:55 a.m.
On Fri, 6 Dec 2013, Sandro Bonazzola wrote:
Error: JAVA_HOME is not defined correctly.
We cannot execute /usr/lib/jvm/java-1.7.0-openjdk.x86_64/bin/java
I suspect the java7 -> java updated filepath name changes are
biting ... the EL 6.5 updates changed things
I see on an updated CentOS 6
[herrold@centos-6 ~]$ rpm -ql java-1.7.0-openjdk | \
grep lib/jvm | grep -v "1.7.0.45"
/usr/lib/jvm-exports/jre-1.7.0-openjdk.x86_64
/usr/lib/jvm-private/java-1.7.0-openjdk.x86_64
/usr/lib/jvm-private/java-1.7.0-openjdk.x86_64/jce
/usr/lib/jvm-private/java-1.7.0-openjdk.x86_64/jce/vanilla
/usr/lib/jvm/jre-1.7.0-openjdk.x86_64
[herrold@centos-6 ~]$ rpm -qf /usr/lib/jvm-exports/jre-1.7.0-openjdk.x86_64
java-1.7.0-openjdk-1.7.0.45-2.4.3.3.el6.x86_64
[herrold@centos-6 ~]$
so there is an added: .45 at the end of the: jre-1.7.0 part
-- Russ herrold
2:14 p.m.
New subject: ovirt_engine_3.3_find_bugs_gerrit failing on JAVA_HOME not defined correctly
Hi,
i just checked and found the source of the problem. (i'll reply to the other threads
on this as well).
We have 2 jenkins slaves (bare metal minidells) that runs from a DMZ lab and can only be
connected
to jenkins master via JNLP connection from slave->master and not via ssh.
this requires that the slave will run a java command [1] to connect to the server with a
specific slave name.
someone by mistake used the same command to connect both of the slaves, so it seemed that
jenkins got confused
between the two and probably had issues finding JAVA_HOME. (the f19 slave actually was
f20).
I've fixed that now and both slaves are connected with their own command.
actions we MUST do to prevent this next time:
1. create new systemd service for the java command via puppet + param on foreman for the
unique ID per host.
2. if you do bring up a host manually - make sure you use the correct command to connect
it.
[1] java -jar slave.jar -jnlpUrl
http://jenkins.ovirt.org/computer/jenkins-slave-host02.ovirt.org/slave-ag... -secret
********************** &
java -jar slave.jar -jnlpUrl
http://jenkins.ovirt.org/computer/jenkins-slave-host01.ovirt.org/slave-ag... -secret
********************** &
Sandro - i've re-triggered all failed gerrit jobs, please check again.
Eyal.
----- Original Message -----
From: "R P Herrold" <herrold(a)owlriver.com>
To: "Sandro Bonazzola" <sbonazzo(a)redhat.com>
Cc: "oVirt infrastructure ML" <infra(a)ovirt.org>
Sent: Friday, December 6, 2013 6:55:29 PM
Subject: ovirt_engine_3.3_find_bugs_gerrit failing on JAVA_HOME not defined correctly
On Fri, 6 Dec 2013, Sandro Bonazzola wrote:
> Error: JAVA_HOME is not defined correctly.
> We cannot execute /usr/lib/jvm/java-1.7.0-openjdk.x86_64/bin/java
I suspect the java7 -> java updated filepath name changes are
biting ... the EL 6.5 updates changed things
I see on an updated CentOS 6
[herrold@centos-6 ~]$ rpm -ql java-1.7.0-openjdk | \
grep lib/jvm | grep -v "1.7.0.45"
/usr/lib/jvm-exports/jre-1.7.0-openjdk.x86_64
/usr/lib/jvm-private/java-1.7.0-openjdk.x86_64
/usr/lib/jvm-private/java-1.7.0-openjdk.x86_64/jce
/usr/lib/jvm-private/java-1.7.0-openjdk.x86_64/jce/vanilla
/usr/lib/jvm/jre-1.7.0-openjdk.x86_64
[herrold@centos-6 ~]$ rpm -qf /usr/lib/jvm-exports/jre-1.7.0-openjdk.x86_64
java-1.7.0-openjdk-1.7.0.45-2.4.3.3.el6.x86_64
[herrold@centos-6 ~]$
so there is an added: .45 at the end of the: jre-1.7.0 part
-- Russ herrold
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
4033
days inactive
4033
days old
2 comments
3 participants
participants (3)
-
Eyal Edri -
R P Herrold -
Sandro Bonazzola