Bug 2087228 - Remove unnecessary steps for importing in document
Summary: Remove unnecessary steps for importing in document
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Documentation
Version: 6.10.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Marie Hornickova
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-17 15:55 UTC by Lucy Fu
Modified: 2023-08-17 00:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-15368 0 None None None 2023-07-31 14:11:20 UTC
Red Hat Issue Tracker SATDOC-942 0 None None None 2022-06-13 15:12:12 UTC

Description Lucy Fu 2022-05-17 15:55:18 UTC
Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html/content_management_guide/using_iss#Importing_a_Repository_content-management

Section Number and Name: 
8.10. Importing into the Library Environment
8.13. Importing a Repository

Describe the issue: 
Steps about repo name and Yum stuff are not needed any more for importing both library and repository.

3. On Satellite Server where you want to import, create/enable repositories the same name and label as the exported content.
4. In the Satellite web UI, navigate to Content > Products, click the Yum content tab and add the same Yum content that the exported Content View version includes.
Suggestions for improvement: 

Additional information: 
Remove steps 3 and 4 for importing library.
Remove steps 3 to 6 for importing repository.

Comment 2 Brad Buckingham 2023-07-21 21:06:39 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.


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