Bug 2182729

Summary: [DDF] The documentation for the connected satellite installation fixed this - you should NEVER run the command like this
Product: Red Hat Satellite Reporter: Direct Docs Feedback <ddf-bot>
Component: InstallerAssignee: satellite6-bugs <satellite6-bugs>
Status: NEW --- QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.12.0CC: ehelms, mjivraja
Target Milestone: UnspecifiedKeywords: Documentation, Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.