This would make a good IDEA.
If you confirm there's no way to do it now, I will create one.
Out of curiosity, did you try using the Red Hat Offline Patch Downloader for this? With the XML config file set like something below?
I've tried this with the offline downloader and it appears to be working so far. I'm waiting for it to finish. But here is a part of the downloader.log so far.
[09 Oct 2014 13:02:58,423] [Thread-1] [INFO] Cleaning existing workspace directory on the destination
[09 Oct 2014 13:02:58,440] [Thread-1] [INFO] Building metadata
[09 Oct 2014 13:02:58,441] [Thread-1] [INFO] Processing all online Channel Update Level filters
[09 Oct 2014 13:03:11,998] [Thread-1] [INFO] Generating the ISO download urls for update level 0 for Red Hat Enterprise Linux Server (v. 6 for 64-bit x86_64)
[09 Oct 2014 13:03:11,998] [Thread-1] [INFO] ISO found for Red Hat Enterprise Linux Server (v. 6 for 64-bit x86_64), download url - https://content-web.rhn.redhat.com/rhn/isos/rhel-6.0/md5sum/f7141396c6a19399d63e8c195354317d/rhel-server-6.0-x86_64-dvd.iso?__gda__=1412874802_4fb3e6a69a94bd75b8f6338cde45cd0e&ext=.iso
[09 Oct 2014 13:03:11,998] [Thread-1] [INFO] Update levels available for Red Hat Enterprise Linux Server (v. 6 for 64-bit x86_64) : [3, 2, 1, 0, 5, 4]
[09 Oct 2014 13:03:14,682] [Thread-2] [INFO] Downloading the ISO for the os architecture RHES6-x86_64, download url: https://content-web.rhn.redhat.com/rhn/isos/rhel-6.0/md5sum/f7141396c6a19399d63e8c195354317d/rhel-server-6.0-x86_64-dvd.iso?__gda__=1412874802_4fb3e6a69a94bd75b8f6338cde45cd0e&ext=.iso
The download part may work, but you'll have a problem with the update part if you're using 8.3 SP3 r175, which forces you to use Update Level filters, you won't be able to update it unless you "fake" update level 1 by renaming the RHES6x86_64U0.xml file to RHES6x86_64U1.xml, even though in reality it's GOLD (or U0 if you prefer).
By that I mean the Update Level filter input field doesn't go below 1.
Just so I understand what you mean. Red Hat releases 6.0 and on day 1 I would call that release "media" or "base." Over the next couple of months, Red Hat releases updates and patches for version 6.0 and at different points in time the RPMs will change. I call this release process 6.0 "patch." Then version 6.1 comes out and they repeat that process.
So what do you consider to be the Gold version of 6.0? Or am I not fully understanding the process on how Red Hat updates their operating systems?
This may help you understand: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/5.6/html/Getting_Started_Guide/sect-Getting_Started_Guide-Channel_Management-Creating_Custom_Channels_From_Specific_Update_Levels.html
Check the example in the syntax of the command they show. GOLD = initial release. So i.e. RHEL 6.0 without updates, basically, what's on the DVD. That's the proper term. I'm surprised nobody seems to be familiar with it.
OK. So you want the GOLD version (base) and you want to keep it that way? So I don't understand what you mean by "you'll have a problem with the update part." If you download the GOLD ISO with the Offline Downloader, extract the RPMs, run the downloader and create the repo, and point a Red Hat 6 Patch Catalog to that repo, how does that not work?
The Catalog update process is done in 2 parts:
1. Download (either online or offline)
2. Update (parses metadata and updates the database/creates depot objects)
Whether the update part is done against a live online repository (pulling latest patches) or done from a static, local one (i.e. extracted iso), the process is more or less the same in the sense it loads new depot objects in the catalog and/or update existing ones.
The update part, when using an Update Level filter, looks for this file: <os><arch>U<update level>.xml (i.e. RHES6x86_64U5.xml for RHEL 6.5 x86_64). Updating the same catalog over and over wouldn't change anything unless you changed the filters to add more os/platforms and there's something more to load.
The problem with r175, is that the input field in the product filter dialog, when selecting Update Level, does not allow you to go below 1.
So, even if it seems to let you type something manually, inputting anything lower than 1 basically sets it to 1 when it's looking for the file.
So in your case, even if the offline downloader generated a proper RHES6x86_64U0.xml file (please confirm if it did), the catalog update job won't be able to use it unless you manually rename it.
Ahh, now I understand. Thank you for the screenshot. Selecting this option in the catalog forces you to select an update level, and it defaults to 1 and doesn't let you go to 0. I wonder what blanking out the number will do (if anything)? I'll test it and see what happens.
Here is what the offline downloader did. I pointed it to this directory (/mnt/store1/patch/redhat-6.0x64-base) and it created the following directory (/mnt/store1/patch/redhat-6.0x64-base/ISO/RHES6-x86_64-U0)
It dropped the rhel-server-6.0-x86_64-dvd.iso in that directory, then extracted the RPMs to the directory I specified.
-r--r--r--. 1 root root 23432244 Oct 9 14:16 kernel-2.6.32-71.el6.x86_64.rpm
According to this I'm at the 6.0 GA version.
I will attempt to create a patch catalog with that metadata and RPMs and see what happens.
I tried blanking out the Update Level, and replacing it with a 0, and it failed with error:
Error while updating feed: Os architecture update level repository xml not found: + sourceFileSystem.generateDisplayPath(fileName)
So I unchecked the Update Level option and I was able to successfully create a patch catalog with the RPMs in the 6.0 GA version.
So my question is, will this still work? Does unchecking this option still give us the desired RPMs and level we want?