Bug #12409: No new host after accepting a salt key - Salt - Foreman

Actions

Copy link

Bug #12409

closed

No new host after accepting a salt key

Added by Tung Dang Quoc over 8 years ago. Updated over 8 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Target version:

Difficulty:

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

When I accept salt key which is same subnet with salt master, new host is created on GUI. But when I accept salt key which is different subnet with salt master, new host is not created on GUI.
Example:
Salt master: 10.90.33.2/24
Node1 : 10.90.33.3/24 -> host is seen on GUI foreman
Node2 : 10.90.34.4/24 -> host is not seen on GUI foreman

Actions

Copy link

Updated by Stephen Benjamin over 8 years ago

Status changed from New to Need more information

Accepting the key alone wouldn't create the host in foreman, it needs to get reported via grains or a highstate report.

Can you try running `foreman-node <hostname of node2>` on the salt master? This triggers uploading the grains to Foreman.

Or run state.highstate and run upload-salt-reports.

If that doesn't work can you share /var/log/foreman/production.log and /var/log/foreman-proxy/proxy.log? Any errors you see in there?

Actions

Copy link

Updated by Tung Dang Quoc over 8 years ago

Stephen Benjamin wrote:

Accepting the key alone wouldn't create the host in foreman, it needs to get reported via grains or a highstate report.

Can you try running `foreman-node <hostname of node2>` on the salt master? This triggers uploading the grains to Foreman.

Or run state.highstate and run upload-salt-reports.

If that doesn't work can you share /var/log/foreman/production.log and /var/log/foreman-proxy/proxy.log? Any errors you see in there?

Thanks Stephen, the new host is appeared on GUI :)

Actions

Copy link