Disconnected Satellite Missing packages after sync

Latest response

After importing the latest incremental iso's (RHEL6 x86_64 dated 12/9/15) I noticed there were a number of extinct package messages coming up during the sync. Running yum update on client machine returns "Error Downloading Packages:
package name: failed to retrieve from channel name
error was [Errno 14] PYCURL ERROE 22 - "The requsted URL returned error 404 Not Found"

MD5 was correct for the iso files. Any one else experiencing this?

Responses

Yes! We are experiencing the same problem, except we are transferring an export of the channels from an updated rhnsat to a disconnected one.

The import of the export works on our RHEL5 Sat 5.4 server, but on a new RHEL6 Sat 5.7 server, we are able to import around 12,225 packages from the base channel and the remaining ~2200 are labeled as extinct and don't get imported. This is also happening to our custom channels as well..

John,

I was able to fix the issue by manually placing the missing packages into their respective location on the Satellite Server itself. All the other needed info was apparently in the iso's, but the rpm's were missing. In our case the packages missing were libxml2-python-2.7.6-20.el6_7.1 libxml2-devel-2.7.6-20-el6_7.1 libxml2-static-2.7.6-20.el6_7.1 libxml2-2.7.6-20.el6_7.1

I haven't checked if they've updated the iso's this week, so maybe it's been fixed. If not you can navigate to the package info page in the web interface. You'll notice that the download button will be grayed out for each one that is missing. On that same page you'll see the directory location where each missing rpm should be placed. You'll have to create the file structure all the way down and then drop the .rpm in there. Hope that helps.

We are having the same issue. It has been a reoccuring issue since last fall. I have been using spacewalk-data-fsck to locate and or remove extinct packages and or incorrect location entries in the database. I know last fall that Redhat forgot to include a NFS-UTILS dependancy (python-argparse) in the incremental export. Here is the article https://access.redhat.com/solutions/1616103. A crappy work around when we pay so much for support. Ever since this happened we have been having issues with the Incremental exports.

Just curious, because we've faced this as well on several occasions,

-- What version of Satellite server are you using?
-- Was this after an ingest of Base or Incremental channels for RHEL 6?

As an aside, this issue at this discussion https://access.redhat.com/discussions/1218823 still exists. That issue is slightly different, it has to do with orphaned RPMS that are yet to ever be updated (such as spacewalk-java, and a collection of others)...

Back to the original point, we have in our history of Satellite server usage (ranging from 5.4.x to 5.7, and now one of our satellite subscriptions is version 6.1.4) have had numerous issues with missing rpms with incremental ISO channel dumps. All eight of our satellite servers are disconnected, and we've suffered the missing rpm issue, and we have had to do as you say above, namely find the missing rpm someplace (often on the satellite server, but not where expected) and through some means make it available. We have had various iterations of this issue under different conditions across several disconnected 5.x Satellite servers for various customers.

We are using Satellite 5.6 installed on RHEL 5. This was an upgrade from Satellite 5.4. This happens after incremental updates. On two occasions I've had to re-import the base content and then import the latest incremental in order to fix all the missing packages. Nice to know I'm not alone.

Hi Daniel,

We've experienced this on numerous versions of the Satellite server. We've had to do the same as you describe in your last reply.

Are you using and embedded postgresql database? We started out using and external oracle database on Oracle RAC but migrated to the embedded with the upgrade from 5.4 to 5.6?

Daniel, yes, we're using the embedded postgresql database, we started using it as our default once it became available, and have been using it ever since.

Close

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