[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Origin 4 on RHEL 6.5

On Tue, Jan 13, 2015 at 10:28:32PM +0100, Massimiliano Dessì wrote:
2015-01-13 21:22 GMT+01:00 Miciah Dashiel Butler Masters <
mmasters redhat com>:

On Tue, Jan 13, 2015 at 07:49:48PM +0000, Massimiliano Dessì wrote:

2015-01-13 19:11 GMT+00:00 Miciah Dashiel Butler Masters <
mmasters redhat com>:

 On Tue, Jan 13, 2015 at 04:43:36PM +0100, Massimiliano Dessě wrote:

 Hi all,
I've installed origin 4 on RHEL  6.5
in a vmware infrastructure,
(deploy with one broker and two nodes)
with the oo_deployment_guide_comprehensive.
When I execute the oo-diagnostics on the node  I receive the follows
in the nodes

[root node02 ~]# oo-diagnostics
FAIL: run_script
oo-accept-node had errors:
FAIL: service ruby193-mcollective not running
FAIL: Could not get SELinux context for ruby193-mcollective
eth0: error fetching interface information: Device not found
FAIL: tc htb qdisc not configured

Are you using a different network interface from eth0? If so, you may
have some configuration where you need to substitute the correct name.
Verify that the EXTERNAL_ETH_DEV setting in /etc/openshift/node.conf is
correct.  Your DHCP configuration may also need to be fixed if it has
the wrong interface name.

in /etc/openshift/node.conf there is EXTERNAL_ETH_DEV=bond0

Is it possible you have the setting duplicated? oo-accept-node reads the

how can check if the setting are duplicated ?

grep EXTERNAL_ETH_DEV /etc/openshift/node.conf

From the ruby command below though, it appears that EXTERNAL_ETH_DEV is
set correctly (the ruby command is running the same code that
oo-accept-node runs to determine the interface name).

about the wrong interface.  Furthermore, there are other tests that
check or use the EXTERNAL_ETH_DEV setting, so I am surprised that only
this test is failing.

What does the command `scl enable ruby193 'ruby -r openshift-origin-common
-e "puts OpenShift::Config.new(OpenShift::Config::NODE_CONF_


What does the command `/sbin/tc qdisc show dev bond0` output?


The code that prints the 'FAIL: tc htb qdisc not configured' error
message is at line 505 of /usr/sbin/oo-accept-node, and it should run if
the shell command at line 503 fails.  There's no obvious way this code
could fail with the error message you got, based on the tests you
performed above.  Perhaps you could try modifying oo-accept-node to add
some puts statements for debugging.  Is $EXTERNAL_ETH_DEV set correctly
at that point? Does qdiscresponse have the expected value? What if you
hardcode bond0 in place of #{$EXTERNAL_ETH_DEV}?

(Hm, it's also not obvious why we have the result variable, but that's
a different matter.)

Miciah Dashiel Butler Masters <mmasters redhat com>

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]