Hide Forgot
1. Proposed title of this feature request Give 'spacewalk-export' the ability to exclude channels from being exported 3. What is the nature and description of the request? When the spacewalk-export tool is used with '--entities=all' (default) or '--entities=channels', it will make a call to the spacewalk-export-channels tool. The spacewalk-export-channels tool will create the repodata information from cloned channels. If there is no backend repo associated with a channel, the tool will also copy the packages ('cp_to_export_dir') If the original Red Hat channels has been removed from syncing by 'spacewalk-channel-remove', any cloned channels will be detected as having no backing repo and will have all of their RPMs copied to the export directory, resulting in potentially a huge export file. Additionally, as the spacewalk-export tool is used for import into Red Hat Satellite 6, there are cases that do not make sense to export. (If it was just repodata, it may not be a big deal, but when it's copying all of the RPMs from the cloned channels, excluding a channel can be much more efficient.) 4. Why does the customer need this? (List the business requirements here) Customer has dozens of cloned channels cloned from EUS versions of RHEL4 and RHEL5. They have since removed them from regular satellite-syncs. This causes the aforementioned copying of the actual RPMs for clone channels they have no interest in importing into Red Hat Satellite 6.x via the transition workflow. 5. How would the customer like to achieve this? (List the functional requirements here) Any mentod of excluding a list of channels from being exported when doing a 'spacewalk-export, or (maybe easier) a flag for 'spacewalk-export', passed to 'spacewalk-export-channels' that says NOT to copy any RPMs whatsoever. 6. For each functional requirement listed in question 5, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Once implemented, they would not have a ${EXPORT_DIR}/[org]/[channel_id] number directory full of unwanted RPMs. 7. Is there already an existing RFE upstream or in Red Hat bugzilla? I do not believe so. 8. Does the customer have any specific timeline dependencies? Customer has begun their project to migrate to Red Hat Satellite 6, and was counting on the ability to export the current state of channels from Satellite 5.x. This recent discovery has made the exports from Satellite 5.x impractical because of the collateral RPMs from many of their other channels. Currently, their transition effort has be halted. 9. Is the sales team involved in this request and do they have any additional input? No. 10. List any affected packages or components. spacewalk-utils 11. Would the customer be able to assist in testing this functionality if implemented? Yes.