Ask Your Question

razor node comes to microkernel but stays there forever

asked 2015-01-06 08:11:45 -0600

Martin gravatar image


This is a PE 3.7.1 configuration on CentOS 6.5 + virtualbox 4.3.12.

Before going to repo, broker, tag and policy, I expect to get the node's facter details from the razor server. But in this case only MAC address is shown.

Basically any tag and policy that I define, does not match the node (even 1=1).

Do you have any idea where to troubleshoot?



edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2015-04-01 20:22:45 -0600

smcclellan gravatar image

updated 2015-04-12 20:29:51 -0600

Hi Mehdi,

The node is expected to remain in the microkernel until it can bind to a policy, at which time it reboots. The microkernel should be sending facts to the razor server in the background.

I would start by running this in the razor-client:

razor nodes # Get the node name for the next query. razor nodes $name --full # This was razor --full nodes $name prior to 0.16.0.

If you're getting the MAC address from the node already, this query should include the rest of the detail.

As for the 1=1 tag not matching, that's odd. A tag like razor create-tag --name all --rule '["=", 1, 1]' should match all nodes. One standard view for debugging is the server log, which should be in /var/log/pe-razor-server/server.log; the /svc/boot messages will inform you of what the new node is sending.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2015-01-06 08:11:45 -0600

Seen: 319 times

Last updated: Apr 12 '15