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.

Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/installation_guide/updating_satellite_server_capsule_server_and_content_hosts#updating_satellite_server_to_next_minor_version

Section Number and Name: 

7.1. Updating Satellite Server --> 6. Perform the update: 

Describe the issue: 

There is no space between the satellite--upgrade step it should read "satellite --upgrade" 

e.g

# satellite-installer --scenario satellite--upgrade --noop

Suggestions for improvement: 

# satellite-installer --scenario satellite --upgrade --noop

Additional information:

Assigning to Misha for review.

Misha - this looks like a good one for us to cherry-pick to the 6.2 branch as well. When the content is merged, you can check out the 6.2 branch and run 'git cherry-pick <commit id>' to copy the change to that branch.

Hello,

This change is now live on the customer portal.

Thank you.

*** Bug 1466910 has been marked as a duplicate of this bug. ***