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.
Description of problem:
Red Hat often has to build disconnected Red Hat content servers (CDNs) at disconnected clients to meet a vital disconnected issue where there are multiple organization's who can't or won't share a Satellite server and won't or can't use an upstream Satellite server. What's more, the disconnected CDN can hold end-of-support software content that customers are still using and do not plan on migrating to a supported version for various reasons.
Satellite 6.12 does allow full content exports in syncable format, the first Pulp 3 release to do so, but....
The hammer content-export --format option is only available for full content exports. Keep in mind that RHEL 8 AppStream and BaseOS are over 100 GB in size, and RHEL 9 won't be far behind. Then there are all of the other large repositories. Red Hat has nearly 6 TB of content at one client and that supports dozens of downstream Satellites, some of which can't be connected to Red Hat's upstream Satellite for various reasons.
I would like to have the "--format" option added to the hammer content-export incremental options list.
Version-Release number of selected component (if applicable): 6.12
How reproducible:
Steps to Reproduce:
1. hammer content-export incremental <library, repository, version> -h
The --format option is not present.
Actual results:
Usage:
hammer content-export incremental version [OPTIONS]
Options:
--async Do not wait for the task
--chunk-size-gb NUMBER Split the exported content into archives no greater than the specified size in
gigabytes.
--content-view[-id] VALUE/NUMBER Name/Id of associated content view
--destination-server VALUE Destination Server name
--fail-on-missing-content Fails if any of the repositories belonging to this version are unexportable.
--from-history-id NUMBER Export history id used for incremental export. If not provided the most recent
export history will be used.
--id NUMBER Content view version id
--lifecycle-environment[-id] VALUE/NUMBER Name/Id of associated lifecycle environment
--organization[-id|-title|-label] VALUE/NUMBER Name/Title/Label/Id of associated organization
--version VALUE Filter versions by version number.
-h, --help Print help
Expected results:
Usage:
hammer content-export incremental version [OPTIONS]
Options:
--async Do not wait for the task
--chunk-size-gb NUMBER Split the exported content into archives no greater than the specified size in
gigabytes.
--content-view[-id] VALUE/NUMBER Name/Id of associated content view
--destination-server VALUE Destination Server name
--fail-on-missing-content Fails if any of the repositories belonging to this version are unexportable.
--format ENUM Export formats. Choose syncable if content is to be imported via repository
sync. Choose importable if content is to be imported via hammer content-import.
--from-history-id NUMBER Export history id used for incremental export. If not provided the most recent
export history will be used.
--id NUMBER Content view version id
--lifecycle-environment[-id] VALUE/NUMBER Name/Id of associated lifecycle environment
--organization[-id|-title|-label] VALUE/NUMBER Name/Title/Label/Id of associated organization
--version VALUE Filter versions by version number.
-h, --help Print help
Additional info:
Also, when a library export is performed, a sort of Content View is created...but it doesn't appear under the Content View list.
Verified in 6.13.0 snap 11.
Tested the Library, Repository and Version exports with yum (custom, RedHat, KS) and file content types.
Yum content exports (which is the main use case) look good - on incremental exports only the newly added packages were exported.
File content exports have an issue - incremental exports still contain the full repo content. Not to block the main use case, the file issue will be tracked under https://bugzilla.redhat.com/show_bug.cgi?id=2172564
Another minor corner-case issue will be tracked under https://bugzilla.redhat.com/show_bug.cgi?id=2172845
Moving this to Failed ON_QA due to
Steps:
1. Import few RedHat, custom and KS repos and enable these repos.
2. Sync the repos and try "hammer content-export complete" with option "--format syncable" for library, repositories and file content types.
3. Add another repository and try "incremental content-export" for the added repository.
Observation:
If export is attempted after changing "on-demand" download policy to "immediate" without re-syncing the repos, it will throw error.
Verified.
Version Tested: Satellite 6.13.0 Snap 17.0
Verification Steps:
1. Enable few RedHat repos and Custom repos.
2. Change the download policy of the repos from on_demand to immediate.
3. Sync the repos.
4. Do the complete content-export for repositories and library with command --format syncable.
5. Enable and few other repos and change the download policy as done earlier and sync the repos.
5. Do the incremental content-export with command --format syncable.
6. Verify that the incremental export should be done properly.
Observation:
Complete and incremental export is successfully completed.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: Satellite 6.13 Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2023:2097
Comment 17Red Hat Bugzilla
2023-09-19 04:30:10 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Description of problem: Red Hat often has to build disconnected Red Hat content servers (CDNs) at disconnected clients to meet a vital disconnected issue where there are multiple organization's who can't or won't share a Satellite server and won't or can't use an upstream Satellite server. What's more, the disconnected CDN can hold end-of-support software content that customers are still using and do not plan on migrating to a supported version for various reasons. Satellite 6.12 does allow full content exports in syncable format, the first Pulp 3 release to do so, but.... The hammer content-export --format option is only available for full content exports. Keep in mind that RHEL 8 AppStream and BaseOS are over 100 GB in size, and RHEL 9 won't be far behind. Then there are all of the other large repositories. Red Hat has nearly 6 TB of content at one client and that supports dozens of downstream Satellites, some of which can't be connected to Red Hat's upstream Satellite for various reasons. I would like to have the "--format" option added to the hammer content-export incremental options list. Version-Release number of selected component (if applicable): 6.12 How reproducible: Steps to Reproduce: 1. hammer content-export incremental <library, repository, version> -h The --format option is not present. Actual results: Usage: hammer content-export incremental version [OPTIONS] Options: --async Do not wait for the task --chunk-size-gb NUMBER Split the exported content into archives no greater than the specified size in gigabytes. --content-view[-id] VALUE/NUMBER Name/Id of associated content view --destination-server VALUE Destination Server name --fail-on-missing-content Fails if any of the repositories belonging to this version are unexportable. --from-history-id NUMBER Export history id used for incremental export. If not provided the most recent export history will be used. --id NUMBER Content view version id --lifecycle-environment[-id] VALUE/NUMBER Name/Id of associated lifecycle environment --organization[-id|-title|-label] VALUE/NUMBER Name/Title/Label/Id of associated organization --version VALUE Filter versions by version number. -h, --help Print help Expected results: Usage: hammer content-export incremental version [OPTIONS] Options: --async Do not wait for the task --chunk-size-gb NUMBER Split the exported content into archives no greater than the specified size in gigabytes. --content-view[-id] VALUE/NUMBER Name/Id of associated content view --destination-server VALUE Destination Server name --fail-on-missing-content Fails if any of the repositories belonging to this version are unexportable. --format ENUM Export formats. Choose syncable if content is to be imported via repository sync. Choose importable if content is to be imported via hammer content-import. --from-history-id NUMBER Export history id used for incremental export. If not provided the most recent export history will be used. --id NUMBER Content view version id --lifecycle-environment[-id] VALUE/NUMBER Name/Id of associated lifecycle environment --organization[-id|-title|-label] VALUE/NUMBER Name/Title/Label/Id of associated organization --version VALUE Filter versions by version number. -h, --help Print help Additional info: Also, when a library export is performed, a sort of Content View is created...but it doesn't appear under the Content View list.