Satellite 6 provisioned host stays in pending install state.

Latest response

Hi,

I have an issue with satellite 6 deployed hosts (both rhel6 and rhel7). After successful install and registration to satellite 6 they remain in pending install status under All Hosts. Anyone else seen this? If I click either of the test hosts they both display runtime statistics and I can install packages from the command line to either of the systems. So for most part everything is fine. Any pointers where to look with this pending install status?

sa
Log in to join the conversation

Responses

sa Community Member 65 points
6 October 2014 1:15 PM

It might be a broken DNS forwarder that is causing this. I have an upstream DNS server that will return a default value for every unknown query. And because of this the client's try to inform that the build has completed causes error:

DNS A Records hostname.sat6domain/ip.returned.by.dns already exists
Completed 409 Conflict in 331ms (ActiveRecord: 20.0ms)

Although the ip address is even from totally different subnet.
I'll see if I can get the dns server fixed by someone. However there seems to be no way to manually set the hosts as Built.

sa Community Member 65 points
15 October 2014 10:06 AM

I turns out that at least in my case the problem was that I had hostname tied to the interface which was out of Satellites control. When I did a reinstall and attached the hostname to the domain that Satellite manages it does not try to look up the hostname form other domains during post install phase. And now I am able to get the client machines to register correctly after kickstart from Satellite 6.

David Powles's picture Red Hat 25369 points
17 October 2014 5:16 AM

Great to hear, Samuli. Thanks for the follow-up.

Mario Gamboa's picture Red Hat Active Contributor 282 points
4 December 2014 2:04 PM

Please read the following documentation:

Red Hat Satellite 6 Provisioning Guide

Todd Walters's picture Expert 851 points
12 December 2016 4:41 PM

Do you have a specific section I should read in this doc? I've read 6.0, 6.1 and 6.2 provisioning guide. I still can't find solution to why sometimes my 6.2 server does NOT delete out entries in pxelinux and tries to provision over and over?

aj Community Member 35 points
26 August 2018 11:07 AM

Hi,

In the provisioning Templates find "PXELinux default local boot" click on template tab and remove "LOCALBOOT 0" and add below 2 entrie then the machine will not go for pxe again after 1 time installed

COM32 chain.c32 APEND hd0

Hope this help.

Regards, -AJ

aj Community Member 35 points
26 August 2018 11:06 AM

Hi,

In the provisioning Templates find "PXELinux default local boot" click on template tab and remove "LOCALBOOT 0" and add below 2 entrie then the machine will not go for pxe again after 1 time installed

COM32 chain.c32 APEND hd0

Hope this help.

Regards, -AJ

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.