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://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Installation_Guide/chap-Red_Hat_Satellite-Installation_Guide-Upgrading_Red_Hat_Satellite_Server_and_Capsule_Server.html#sect-Red_Hat_Satellite-Installation_Guide-Upgrading_Red_Hat_Satellite_Server_and_Capsule_Server-Upgrading_Red_Hat_Satellite
This was reported from a customer.
1. /opt is required to be specific size. The customer case, the required size was 2G and 1.3G being set. The consultant increased the partition to 5G to get the upgrade going, but after the upgrade, the usage dropped down to 1.3G again.
The docs 1) need to specify some kind of sizing guidelines and 2) cover *what* the directory is being used for (like temporary storage during the upgrade).
2. The "katello-upgrade" example changes some settings from 6.0. The consultant specifies:
* Proxy settings. If you have special characters in the password, you need to get your escape characters right or it won't work.
* TFTP settings
I don't know if this is specified (I haven't checked), but I do know that the Satellite files are not supposed to be edited directly. If they are edited outside of the katello-* commands, then it loses that configuration if katello-install (and possibly katello-upgrade?) is ever run.
3. Sat 6.1 requires new channel called "Red Hat Satellite 6.1 Tools
Channel," so the manifest needs to be recreated to include the channel. Also, recreating the manifest may require removing all the subscriptions from
the Satellite entry in the portal and adding things back. When the consultant did this, he encountered a database error. The error isn't in the email, but that may need to be mentioned or there may be a workaround.
(In reply to Deon Ballard from comment #0)
>
> 2. The "katello-upgrade" example changes some settings from 6.0. The
> consultant specifies:
>
> * Proxy settings. If you have special characters in the password, you need
> to get your escape characters right or it won't work.
>
Re the above, see
Bug 1259975 - RFE: Document list of characters to escape in password configuration
https://bugzilla.redhat.com/show_bug.cgi?id=1259975#c3