Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionStephen Wadeley
2016-06-09 12:05:30 UTC
Document URL:
https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Transition_Guide/sect-Red_Hat_Satellite-Transition_Guide-Transitioning_from_Satellite_5_to_6-Exporting_Entities_from_Satellite_5.html
Section Number and Name:
3.6. Exporting Entities from Satellite 5
Red_Hat_Satellite-Transition_Guide-6.1-en-US-2-10
Describe the issue:
Running the exports directly on the Satellite 5 Server allows complete access to the spacewalk-export functionality, including limiting the data exported, using the --where and --like options. However, if the goal is to export as much as possible, or at most limit by organization, the spacewalk-export tool can manage the process for you.
The --where and --like options are for spacewalk-report, not spacewalk-export. For example, the results for spacewalk-export --help:
[root@sat5 satellite]# spacewalk-export --help
Usage: spacewalk-export [options]
Options:
-h, --help show this help message and exit
Locations:
Where do you want to export to?
--export-dir=DIR Specify directory to store exports in (will be created
if not found) - defaults to /root/spacewalk-export-dir
--export-package=FILE
Specify filename to use for final packaged-exports
tarfile - defaults to spacewalk_export.tar.gz
Entities:
What do you want to export?
--list-entities List supported entities
--entities=entity[,entity...]
Specify comma-separated list of entities to export
(default is all)
--org=ORG-ID Specify an org-id whose data we will export
--dump-repos Dump contents of file: repositories
Channels:
--ext-pkgs Channel-output contains only external packages
--skip-repogen Omit repodata generation for exported channels
--no-size Do not check package size
Utility:
--clean How do I clean up from previous runs?
--debug Log debugging output
--quiet Log only errors
The spacewalk-export calls spacewalk-report with the --where option (couldn’t find any reference to using --find), but a user can’t include --where or --like options when they run spacewalk-export. This leads me to believe this paragraph meant to say spacewalk-report in the first sentence.
Suggestions for improvement:
Suggestion: "Running the exports directly on the Satellite 5 Server allows complete access to the spacewalk-report functionality…"
Additional information:
Thanks to Dan Macpherson for reporting this issue.
I can confirm spacewalk-export command internally calls spacewalk-report.
--where-<column-id> and --like-<column-id> are really spacewalk-report options, no spacewalk-export options.
My proposed change would be:
=============================
Running the exports directly on the Satellite 5 server allows complete access to the spacewalk-export functionality, including limiting the data exported, using the --where and --like options.
---->>>
Running the exports directly on the Satellite 5 server allows complete access to the spacewalk-report functionality, including limiting the data exported, using the --where and --like options.
=============================
Additionally, following sentence isn't correct
=============================
Using this format calls both spacewalk-report-channels and spacewalk-export-channels, and consequently exports both Red Hat and non-Red Hat channels.
=============================
as spacewalk-report-channels does not exist. I'm not sure, what this sentence tries to say.
(In reply to Tomas Lestach from comment #3)
> Additionally, following sentence isn't correct
> =============================
> Using this format calls both spacewalk-report-channels and
> spacewalk-export-channels, and consequently exports both Red Hat and non-Red
> Hat channels.
> =============================
> as spacewalk-report-channels does not exist. I'm not sure, what this
> sentence tries to say.
Typo - should be "...calls both 'spacewalk-report channels' and 'spacewalk-export-channels'..."