Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_satellite/6.3-beta/html-single/upgrade_guide/

Section Number and Name: 
1.4. Upgrading Capsule Servers - Step 11.

# satellite-installer --scenario capsule --upgrade \
--capsule-certs-tar mycapsule.example.com-certs.tar

Describe the issue: 
Apparently, capsule scenario option --capsule-certs-tar is now --foreman-proxy-content-certs-tar

Also 

https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_satellite/6.3-beta/html-single/installation_guide/

4.6.1. Configuring Capsule Server with a Default Server Certificate - Step 4.

# satellite-installer --scenario capsule \
--capsule-parent-fqdn "satellite.example.com" \
--foreman-proxy-register-in-foreman "true" \
--foreman-proxy-foreman-base-url "https://satellite.example.com" \
--foreman-proxy-trusted-hosts "satellite.example.com" \
--foreman-proxy-trusted-hosts "mycapsule.example.com" \
--foreman-proxy-oauth-consumer-key "UVrAZfMaCfBiiWejoUVLYCZHT2xhzuFV" \
--foreman-proxy-oauth-consumer-secret \
"ZhH8p7M577ttNU3WmUGWASag3JeXKgUX" \
--capsule-pulp-oauth-secret "TPk42MYZ42nAE3rZvyLBh7Lxob3nEUi8" \
--capsule-certs-tar "~/mycapsule.example.com-certs.tar"   <<< BAD

But this occurence is not so severe as the one in Upgrade Guide since this command is usually proposed by capsule-certs-generate in Step 1.

Assigning to Stephen for review.

Stephen - some feedback items for the Capsule Server upgrade section.

Updating the doc type.