Let me preface this with “I’m not a Linux Admin, I just represent some at work!”
We deployed a set of actions last night from the Red Hat Enterprise 5 & 6 Native Tools sites to a collection of machines.
The servers are all configured to use the same repository, a Satellite server.
The IEM Action showed all of the machines failed to download the required .RPM files. The Linux admins tell me that the files are on the Satellite server. They can manually install the patches via a manual execution of YUM.
Can someone recommend where I should start looking to determine why IEM is failing to download these files? It happened on both Red Hat 5 & Red Hat 6 servers.
Did any of these RPM’s have prerequisites that are NOT on your repository? Remember we do try and install what is needed to install the RPM’s that you are trying to install. I’d leave it up to the patch guys to answer specifically but that could be the issue.
Did you configure the RHEL download plug-in in the patch support site dashboard and run the associated RHEL fixlet to enable use of custom repositories? Either of those can cause this condition.
It was my understanding that the Native Tools content was supposed to use the Red Hat Satellite repository that the servers were already pointed to, not download content from Red Hat directly.
@TimRice, I could be wrong, but I believe you still have to run the fixlet to enable custom repos (fixlet ID 13 in Patching Support site) if you want to leverage an internal satellite.
@cmcannady, you are right. In order to make use of custom repositories/satellites one should enable custom repos on the selected endpoint by taking an action on the task 13 of Patching Support site.
The default behavior of the native tools fixlets is similar to EDR sites; simply, resolve the dependencies using the yum metadata we provide and request the binary downloads from RHN via the download plugin. Once the custom repo enable task is actioned, the behavior of the patch fixlets for the respective endpoint will change and fixlets will just invoke yum as if it is invoked from the command line.