Bug 2059388 - [RFE] add option to export and import just repository for hammer content-export
Summary: [RFE] add option to export and import just repository for hammer content-export
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Inter Satellite Sync
Version: 6.10.1
Hardware: Unspecified
OS: Unspecified
high
medium with 4 votes
Target Milestone: 6.10.4
Assignee: Partha Aji
QA Contact: Radek Mynar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-28 22:29 UTC by Brad Buckingham
Modified: 2023-09-15 01:22 UTC (History)
13 users (show)

Fixed In Version: tfm-rubygem-katello-4.1.1.50-1,tfm-rubygem-hammer_cli_katello-1.1.2.4-1
Doc Type: Enhancement
Doc Text:
Clone Of: 2028377
Environment:
Last Closed: 2022-03-29 14:48:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 34374 0 Normal Closed [RFE] add option to export and import just repository for hammer content-export 2022-02-28 22:29:19 UTC
Red Hat Issue Tracker SAT-6677 0 None None None 2022-02-28 22:29:19 UTC
Red Hat Issue Tracker SAT-8689 0 None None None 2022-02-28 22:33:31 UTC
Red Hat Product Errata RHBA-2022:1116 0 None None None 2022-03-29 14:49:01 UTC

Comment 3 John G 2022-03-07 15:45:37 UTC
This fix for 6.10.4 shold allow repo export product to be the same as Sat6.9 and earlier!  It needs to be able to allow disconnected satellite import via sync as if connected to CDN - NOT a kludge like the 6.10.x content-view export.  All rpm's/repo should be available via directory structure - i.e Red Hat Enterprise Linux 7 Server RPMs x86_64 7Server would be located under ${export_dir}/content/dist/rhel/server/7/7Server/x86_64/os - just like an import from REDHAT CDN.

Comment 7 Brad Buckingham 2022-03-21 15:03:50 UTC
(In reply to John G from comment #3)
> This fix for 6.10.4 shold allow repo export product to be the same as Sat6.9
> and earlier!  It needs to be able to allow disconnected satellite import via
> sync as if connected to CDN - NOT a kludge like the 6.10.x content-view
> export.  All rpm's/repo should be available via directory structure - i.e
> Red Hat Enterprise Linux 7 Server RPMs x86_64 7Server would be located under
> ${export_dir}/content/dist/rhel/server/7/7Server/x86_64/os - just like an
> import from REDHAT CDN.

Hello John,

This bugzilla for 6.10.4 will not include the format that you are requesting.  The teams are working towards that and we will be tracking it using a separate bugzilla.  I will add a reference to that bugzilla, once available.  Thanks!

Comment 8 John G 2022-03-21 15:31:26 UTC
Thanks for the update Brad - please provide the new BZ and please bump up it's priority so it's included in 6.10.x or 6.11 thanks.  This is needed ASAP as 6.10 CV export/import  has way tooooo many problems.

Comment 9 Radek Mynar 2022-03-22 17:19:35 UTC
I's now possible to export and import repositories in the same way as library and CVs since 6.10.

VERIFIED with Satellite 6.10.4 SNAP 3.0

Comment 10 John G 2022-03-22 17:41:59 UTC
Radek, Thanks for the update - but need export and import repositories in the same way as repositories and CVs since 6.9 and earlier as Brad noted will be in new BZ and implemented ASAP.

Comment 12 Brad Buckingham 2022-03-29 12:59:43 UTC
Bug 2069306 has been created, as mentioned in comment 7.

John, for awareness, due to the nature of the changes required, it is unlikely that this can be backported (once available) to 6.10.z.

Thanks!

Comment 16 errata-xmlrpc 2022-03-29 14:48:54 UTC
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 (Satellite 6.10.4 Async Bug Fix Update), 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/RHBA-2022:1116

Comment 17 Red Hat Bugzilla 2023-09-15 01:22:28 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


Note You need to log in before you can comment on or make changes to this bug.