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

Re: Origin 4 problem to add nodes to district

On Wed, Jan 14, 2015 at 01:55:29PM +0000, Massimiliano Dessì wrote:
HI all,
the oo-mco ping show  the two nodes,
but when I try to add with
oo-admin-ctl-district -c add-node -n small_district -i <node>
I receive the message
"ERROR OUTPUT: Cannot connect to node."

It might be worth trying `oo-admin-ctl-district -c add-node -n
small_district --available` to see whether the command works without
explicitly providing the node's identity.

Note: I'v eapplyed the patch
to correct the bug https://bugzilla.redhat.com/show_bug.cgi?id=1122339)

The mcollective/server.cfg point to

Is /opt/rh/ruby193/root/etc/mcollective/facts.yaml being updated? The
/etc/cron.minutely/openshift-facts cronjob should update facts.yaml
once every minute.  If facts.yaml isn't being updated, try running
`oo-exec-ruby /opt/rh/ruby193/root/usr/libexec/mcollective/update_yaml.rb`
manually to see whether that fails or whether cron is misconfigured.

The oo-mco facts node-profile -v

That should be 'node_profile', with an underscore.

show a message no response from the two nodes.

Any hints to fix ?

What does `oo-mco facts kernel` show? Should be 'Linux' (same as the
output of `uname -s`).

How about `oo-mco inventory <node>`?

Thanks in advance

users mailing list
users lists openshift redhat com

Miciah Dashiel Butler Masters <mmasters redhat com>

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