Bug 2182729 - [DDF] The documentation for the connected satellite installation fixed this - you should NEVER run the command like this
Summary: [DDF] The documentation for the connected satellite installation fixed this -...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installer
Version: 6.12.0
Hardware: All
OS: All
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-29 13:06 UTC by Direct Docs Feedback
Modified: 2023-08-08 14:57 UTC (History)
2 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-16825 0 None None None 2023-03-29 13:09:17 UTC

Description Direct Docs Feedback 2023-03-29 13:06:19 UTC
The documentation for the connected satellite installation fixed this - you should NEVER run the command like this - you should always include an organization and location.  See the comments in the Connected Satellite for why.

Reported by: vzdansmith

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html/installing_satellite_server_in_a_disconnected_network_environment/installing_server_disconnected_satellite#annotations:42eab92f-6c7e-492a-b480-298bbe99fa74

Comment 2 Marie Hornickova 2023-03-30 09:39:43 UTC
Hello,

Thank you very much for reporting this suggestion for improvement.

The information about the progress on implementation will be shared in this ticket.

Thank you!

Comment 5 Eric Helms 2023-04-27 16:48:07 UTC
We should opt to make two changes:

 1) Update the disconnected install script to have better output message that simply indicates success and the next action.
 2) Update the documentation according to the resulting updates from #1.

So this is a development change first, and then a docs update.


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